zeeboo

15 ms·

1. 121.▲
   by zeeboo 14y ago

   It's typedObj, ok = something.(type) just like it is with maps, or any other ", ok" thing. http://play.golang.org/p/I-5kD88knC
2. 122.▲
   by zeeboo 14y ago

   You can abstract the channel operations behind interfaces and regain type safety. Inspired by the sort package, I wrote http://thegoods.biz/broadcast for doing broadcast type patterns safely. To use it you implement two trivial methods on
3. 123.▲
   by zeeboo 14y ago

   No you can't: http://play.golang.org/p/I_pu9oG1uF
4. 124.▲
   by zeeboo 14y ago

   Oops, I called fib(-1) on the example page :(
5. 125.▲
   by zeeboo 14y ago

   I can't answer why GPUs weren't considered, though I'd guess because they weren't as familiar with the numbers and this was a "back of the envelope" calculation. The reason why I wouldn't take into account better attacks is because that's m
6. 126.▲
   by zeeboo 14y ago

   Not surprisingly, I completely disagree. While this individual line of code may seem particularly offensive, it was written that way to be extremely clear and minimize dependencies. A more structured web app would be doing much more with th
7. 127.▲
   by zeeboo 14y ago

   Sorry about that! I took the suggestion and changed it to just $