Adam Brocklebank

Adam Brocklebank (born 6 September 1995)[1] is an English rugby union player for Newcastle Falcons in Premiership Rugby. His preferred position is as a Prop.

Adam Brocklebank
Birth nameAdam Thomas Brocklebank
Date of birth (1995-09-06) 6 September 1995
Place of birthOrmskirk, England
Height1.88 m (6 ft 2 in)
Weight125 kg (19 st 10 lb)
UniversityDurham University
Rugby union career
Position(s) Loosehead Prop
Amateur team(s)
Years Team Apps (Points)
Ormskirk Rugby Club
Mysercough College		 ()
Senior career
Years Team Apps (Points)
2014– Newcastle Falcons 22 (0)
Correct as of 19 May 2019

Club career

Brocklebank was a late-comer to rugby, first showing interest into the sport at the age of 16. initially a back row, Brocklebank played his first games for Ormskirk Rugby Club and Myerscough College. After beginning his studies at Durham University, Brocklebank was spotted by Newcastle Falcons and represented the club's A-League team in 2014/15 before signing with the Falcons' senior academy the following summer. He was awarded a senior contract in February 2017, to begin the following season after the end of his degree.[2]

In his new role as a prop, Brocklebank has represented both England Counties U18s and England Students. He made his first team debut during the 2016-2017 season.[3]

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.
gollark: Oh, and the error handling is terrible and it's kind of the type system's fault.

References
  1. "Adam Brocklebank". ESPN. Retrieved 3 December 2018.
  2. "Congratulations Adam Brocklebank". Durham University Rugby. Retrieved 31 December 2018.
  3. "Newcastle Falcons Profile". Newcastle Falcons. Retrieved 27 November 2018.
This article is issued from Wikipedia. The text is licensed under Creative Commons - Attribution - Sharealike. Additional terms may apply for the media files.