2018 Garden Open – Doubles
Andreas Mies and Oscar Otte were the defending champions but only Mies chose to defend his title, partnering Kevin Krawietz. Mies successfully defended his title.
Doubles | |
---|---|
2018 Garden Open | |
Champions | ![]() ![]() |
Runners-up | ![]() ![]() |
Final score | 6–3, 2–6, [10–4] |
Krawietz and Mies won the title after defeating Sander Gillé and Joran Vliegen 6–3, 2–6, [10–4] in the final.
Seeds
Sander Gillé / Joran Vliegen (Final) Denys Molchanov / Igor Zelenay (Quarterfinals) Kevin Krawietz / Andreas Mies (Champions) Marin Draganja / Tomislav Draganja (Quarterfinals)
Draw
Key
- Q = Qualifier
- WC = Wild Card
- LL = Lucky Loser
- Alt = Alternate
- SE = Special Exempt
- PR = Protected Ranking
- ITF = ITF entry
- JE = Junior Exempt
- w/o = Walkover
- r = Retired
- d = Defaulted
First Round | Quarterfinals | Semifinals | Final | ||||||||||||||||||||||||
1 | ![]() ![]() | 77 | 6 | ||||||||||||||||||||||||
![]() ![]() | 62 | 3 | 1 | ![]() ![]() | 6 | 6 | |||||||||||||||||||||
WC | ![]() ![]() | 4 | 5 | ![]() ![]() | 3 | 0 | |||||||||||||||||||||
![]() ![]() | 6 | 7 | 1 | ![]() ![]() | w/o | ||||||||||||||||||||||
4 | ![]() ![]() | 6 | 2 | [10] | WC | ![]() ![]() | |||||||||||||||||||||
![]() ![]() | 3 | 6 | [4] | 4 | ![]() ![]() | 5 | 4 | ||||||||||||||||||||
WC | ![]() ![]() | 6 | 6 | WC | ![]() ![]() | 7 | 6 | ||||||||||||||||||||
![]() ![]() | 4 | 4 | 1 | ![]() ![]() | 3 | 6 | [4] | ||||||||||||||||||||
![]() ![]() | 4 | 5 | 3 | ![]() ![]() | 6 | 2 | [10] | ||||||||||||||||||||
![]() ![]() | 6 | 7 | ![]() ![]() | 4 | 5 | ||||||||||||||||||||||
![]() ![]() | 1 | 4 | 3 | ![]() ![]() | 6 | 7 | |||||||||||||||||||||
3 | ![]() ![]() | 6 | 6 | 3 | ![]() ![]() | 6 | 6 | ||||||||||||||||||||
![]() ![]() | 2 | 4 | ![]() ![]() | 4 | 2 | ||||||||||||||||||||||
![]() ![]() | 6 | 6 | ![]() ![]() | 6 | 6 | ||||||||||||||||||||||
WC | ![]() ![]() | 1 | 3 | 2 | ![]() ![]() | 2 | 3 | ||||||||||||||||||||
2 | ![]() ![]() | 6 | 6 |
gollark: You can use codegen to generate code for repetitive tasks of some sort if they don't need to generalize much or go outside your project, but it's much better to just... not have to do those repetitive tasks, or have the compiler/macros handle them.
gollark: Also, you end up with a mess of fragile infrastructure which operates on stringy representations of the code.
gollark: I can either:- use `interface{}` - lose type safety and performance- codegen a different `Tree` type for every use of it - now I can't really put it in its own library and it's generally inelegant and unpleasant
gollark: Consider what happens if I want to implement a generic `Tree` type.
gollark: For one thing, it doesn't really work in many cases.
References
This article is issued from Wikipedia. The text is licensed under Creative Commons - Attribution - Sharealike. Additional terms may apply for the media files.