jtasdlfj234

3 ms·

1. 1.▲
   by jtasdlfj234 3y ago

   Virtual Threads, under the hood, cooperatively yield at IO boundaries (on supported APIs)
2. 2.▲
   by jtasdlfj234 3y ago

   Please prove me wrong on these points. My current belief and understanding is that: 1. `foo(T)` indicates polymorphic over both `T::T(const T&)` and `T::T(T&&)`. This gives you benefits of both pass-by-move (using `std::move` as
3. 3.▲
   by jtasdlfj234 3y ago

   Okay, circling back here. So your position is that nil safety would reduce the value of Go's "getting things done"? As someone who uses Go in production, I don't agree at all.
4. 4.▲
   by jtasdlfj234 3y ago

   Dart evolved into a nice language with null-safety and exhaustive patterns. Hopefully in Go 3, we could see these features added as well.
5. 5.▲
   by jtasdlfj234 3y ago

   > It's so derpy. That's why I love it.
6. 6.▲
   by jtasdlfj234 3y ago

   Excellently described. I'd love to see a resource that highlights these all on a table across programming languages as well as the associated strengths and weaknesses of such threading & concurrency models. Perhaps a ByteByteGo gra
7. 7.▲
   by jtasdlfj234 3y ago

   I would have more respect if they at least admitted to the flawed type system but instead say it is not a problem. It is disappointing to see past mistakes repeated in a new programming language. Even the Java language creator was humble en