2013 Kazan Kremlin Cup – Doubles
Sanchai Ratiwatana and Sonchat Ratiwatana were the defending champions, but both players chose not to participate.
Radu Albot and Farrukh Dustov won the title defeating Egor Gerasimov and Dzmitry Zhyrmont 6–2, 6–7(3–7), [10–7].
Doubles | |
---|---|
2013 Kazan Kremlin Cup | |
Champions | ![]() ![]() |
Runners-up | ![]() ![]() |
Final score | 6–2, 6–7(3–7), [10–7] |
Seeds
Dominik Meffert / Philipp Oswald (First Round, Withdrew) Rameez Junaid / Frank Moser (Quarterfinals) James Cerretani / Adil Shamasdin (First Round) Mikhail Elgin / Teymuraz Gabashvili (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
Draw
First Round | Quarterfinals | Semifinals | Final | ||||||||||||||||||||||||
1 | ![]() ![]() | ||||||||||||||||||||||||||
![]() ![]() | w/o | ![]() ![]() | 6 | 6 | |||||||||||||||||||||||
WC | ![]() ![]() | 3 | 2 | ![]() ![]() | 2 | 4 | |||||||||||||||||||||
![]() ![]() | 6 | 6 | ![]() ![]() | 63 | 6 | [6] | |||||||||||||||||||||
4 | ![]() ![]() | 6 | 2 | [10] | ![]() ![]() | 77 | 3 | [10] | |||||||||||||||||||
![]() ![]() | 1 | 6 | [7] | 4 | ![]() ![]() | 6 | 3 | [7] | |||||||||||||||||||
WC | ![]() ![]() | 0 | 79 | [9] | ![]() ![]() | 3 | 6 | [10] | |||||||||||||||||||
![]() ![]() | 6 | 67 | [11] | ![]() ![]() | 2 | 77 | [7] | ||||||||||||||||||||
WC | ![]() ![]() | 4 | 65 | ![]() ![]() | 6 | 63 | [10] | ||||||||||||||||||||
![]() ![]() | 6 | 77 | ![]() ![]() | 3 | 6 | [10] | |||||||||||||||||||||
![]() ![]() | 66 | 6 | [10] | ![]() ![]() | 6 | 4 | [6] | ||||||||||||||||||||
3 | ![]() ![]() | 78 | 4 | [1] | ![]() ![]() | 6 | 6 | ||||||||||||||||||||
![]() ![]() | 0 | 4 | ![]() ![]() | 3 | 4 | ||||||||||||||||||||||
![]() ![]() | 6 | 6 | ![]() ![]() | 6 | 1 | [10] | |||||||||||||||||||||
![]() ![]() | 6 | 4 | [3] | 2 | ![]() ![]() | 2 | 6 | [6] | |||||||||||||||||||
2 | ![]() ![]() | 2 | 6 | [10] |
gollark: As a Go developer, you have surely encountered at some point something using the `container` package, containing things like `container/ring` (ring buffers), `container/list` (doubly linked list), and `container/heap` (heaps, somehow). You may also have noticed that use of these APIs requires `interface{}`uous type casting. As a Go developer you almost certainly do not care about the boilerplate, but know that this makes your code mildly slower, which you ARE to care about.
gollark: High demand for generics by programmers around the world is clear, due to the development of languages like Rust, which has highly generic generics, and is supported by Mozilla, a company. As people desire generics, the market *is* to provide them.
gollark: Hmm.
gollark: Interesting!
gollark: In languages such as Haskell, generics are extremely natural. `data Beeoid a b = Beeoid a | Metabeeoid (Beeoid b a) a | Hyperbeeoid a b a b` trivially defines a simple generic data type. It is only in the uncoolest of languages that this simplicity has been stripped away, with generic support artificially limited to a small subset of types, generally just arrays and similar structures. Thus, reject no generics, return to generalized, simple and good generics.
References
This article is issued from Wikipedia. The text is licensed under Creative Commons - Attribution - Sharealike. Additional terms may apply for the media files.