1909–10 Missouri Tigers men's basketball team
The 1909–10 Missouri Tigers men's basketball team represented University of Missouri in the 1909–10 college basketball season. The team was led by second year head coach Guy Lowman. The captain of the team was Frank Burress.
1909–10 Missouri Tigers men's basketball | |
---|---|
Conference | Big Eight Conference |
1909–10 record | 8–11 (3–7 MVIAA) |
Head coach | Guy Lowman |
Home arena | Rothwell Gymnasium |
Missouri finished with an 8–11 record overall and a 3–7 record in the Missouri Valley Conference. This was good enough for a 3rd-place finish in the regular season conference standings.
Schedule and results
Date time, TV |
Rank# | Opponent# | Result | Record | Site city, state | ||||||
---|---|---|---|---|---|---|---|---|---|---|---|
January 10* |
William Jewell | W 42–19 | 1–0 |
Columbia, Missouri | |||||||
January 11* |
William Jewell | W 37–35 | 2–0 |
Columbia, Missouri | |||||||
January 13 |
Washington (MO) | W 25–10 | 3–0 (1–0) |
Columbia, Missouri | |||||||
January 14 |
Washington (MO) | W 30–9 | 4–0 (2–0) |
Columbia, Missouri | |||||||
January 21* |
Grinnell | L 30–34 | 4–1 (2–0) |
Columbia, Missouri | |||||||
January 22* |
Grinnell | L 8–32 | 4–2 (2–0) |
Columbia, Missouri | |||||||
February 5* |
Emporia State | W 32–8 | 5–2 (2–0) |
Columbia, Missouri | |||||||
February 9* |
at Central Missouri | W 28–27 | 6–2 (2–0) |
Warrensburg, Missouri | |||||||
February 10* |
at Central Missouri | W 20–19 | 7–2 (2–0) |
Warrensburg, Missouri | |||||||
February 11 |
at Kansas | L 15–29 | 7–3 (2–1) |
Lawrence, Kansas | |||||||
February 12 |
at Kansas | L 14–27 | 7–4 (2–2) |
Lawrence, Kansas | |||||||
February 14 |
at Drake | W 28–7 | 8–4 (3–2) |
Des Moines, Iowa | |||||||
February 15 |
at Iowa State | L 11–13 | 8–5 (3–3) |
Ames, Iowa | |||||||
February 16* |
at Iowa | L 6–20 | 8–6 (3–3) |
Iowa City, Iowa | |||||||
February 21 |
Kansas | L 21–25 | 8–7 (3–4) |
Columbia, Missouri | |||||||
February 22 |
Kansas | L 22–58 | 8–8 (3–5) |
Columbia, Missouri | |||||||
February 28 |
at Washington (MO) | L 12–24 | 8–9 (3–6) |
St. Louis, Missouri | |||||||
March 1 |
at Washington (MO) | L 13–35 | 8–10 (3–7) |
St. Louis, Missouri | |||||||
March 23* |
MO Athletic Club | L 22–32 | 8–11 (3–7) |
Columbia, Missouri | |||||||
*Non-conference game. #Rankings from Coaches' Poll. (#) Tournament seedings in parentheses. All times are in Central Standard Time. |
gollark: Well, yes, but they're byte sequences.
gollark: I mean, it's better than C and stuff, and I wouldn't mind writing simple apps in it.
gollark: Speaking specifically about the error handling, it may be "simple", but it's only "simple" in the sense of "the compiler writers do less work". It's very easy to mess it up by forgetting the useless boilerplate line somewhere, or something like that.
gollark: Speaking more generally than the type system, Go is just really... anti-abstraction... with, well, the gimped type system, lack of much metaprogramming support, and weird special cases, and poor error handling.
gollark: - They may be working on them, but they initially claimed that they weren't necessary and they don't exist now. Also, I don't trust them to not do them wrong.- Ooookay then- Well, generics, for one: they *kind of exist* in that you can have generic maps, channels, slices, and arrays, but not anything else. Also this (https://fasterthanli.me/blog/2020/i-want-off-mr-golangs-wild-ride/), which is mostly about the file handling not being good since it tries to map on concepts which don't fit. Also channels having weird special syntax. Also `for` and `range` and `new` and `make` basically just being magic stuff which do whatever the compiler writers wanted with no consistency- see above- Because there's no generic number/comparable thing type. You would need to use `interface{}` or write a new function (with identical code) for every type you wanted to compare- You can change a signature somewhere and won't be alerted, but something else will break because the interface is no longer implemented- They are byte sequences. https://blog.golang.org/strings.- It's not. You need to put `if err != nil { return err }` everywhere.
References
- "University of Missouri, Official Athletic Site of the Mizzou Tigers University of Missouri". Archived from the original on 2008-12-11. Retrieved 2008-05-31.
This article is issued from Wikipedia. The text is licensed under Creative Commons - Attribution - Sharealike. Additional terms may apply for the media files.