2018 Sparkassen ATP Challenger – Doubles
Sander Arends and Antonio Šančić were the defending champions but only Šančić chose to defend his title, partnering Purav Raja. Šančić lost in the finals to Sander Gillé and Joran Vliegen.
Doubles | |
---|---|
2018 Sparkassen ATP Challenger | |
Champions | |
Runners-up | |
Final score | 3–6, 6–3, [10–3] |
Gillé and Vliegen won the title after defeating Raja and Šančić 3–6, 6–3, [10–3] in the final.
Seeds
Luke Bambridge / Jonny O'Mara (Semifinals) Kevin Krawietz / Andreas Mies (Semifinals) Purav Raja / Antonio Šančić (Final) Sander Gillé / Joran Vliegen (Champions)
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 | 6 | 66 | [10] | ||||||||||||||||||||||||
3 | 78 | [8] | 1 | w/o | |||||||||||||||||||||||
6 | 65 | [7] | WC | ||||||||||||||||||||||||
WC | 3 | 77 | [10] | 1 | 77 | 63 | [6] | ||||||||||||||||||||
4 | 77 | 7 | 4 | 64 | 77 | [10] | |||||||||||||||||||||
WC | 65 | 5 | 4 | 6 | 6 | ||||||||||||||||||||||
WC | 5 | 62 | 4 | 4 | |||||||||||||||||||||||
7 | 77 | 4 | 3 | 6 | [10] | ||||||||||||||||||||||
6 | 7 | 3 | 6 | 3 | [3] | ||||||||||||||||||||||
2 | 5 | ||||||||||||||||||||||||||
62 | 3 | 3 | w/o | ||||||||||||||||||||||||
3 | 77 | 6 | 3 | 7 | 77 | ||||||||||||||||||||||
6 | 4 | [6] | 2 | 5 | 62 | ||||||||||||||||||||||
4 | 6 | [10] | 3 | 77 | [4] | ||||||||||||||||||||||
65 | 6 | [6] | 2 | 6 | 62 | [10] | |||||||||||||||||||||
2 | 77 | 3 | [10] |
gollark: I quite like the `#[]` thing, it seems neat.
gollark: Solution: remove libraries.
gollark: > and rust's syntax is a horrible tradeoff :PWhy? It seems pretty C-ish. I quite like it.
gollark: > there are tools that prevent you from doing unsafe thingsThey don't seem to be hugely *good* at it, or at least aren't deployed enough, given the massive frequency of memory-related bugs in C projects.
gollark: People make mistakes and you can't just tell them not to. Even SQLite, which is ridiculously extensively tested and has very skilled developers, has bugs sometimes. If a language can prevent significant classes of mistake without horrible tradeoffs, that is a good thing to have.
References
This article is issued from Wikipedia. The text is licensed under Creative Commons - Attribution - Sharealike. Additional terms may apply for the media files.