bowlerman

5 ms·

1. 1.▲
   by bowlerman 4y ago

   Big-name crates that do IO often use async by default, but I haven't seen one so far that doesn't provide a sync/blocking api as well. Usually this is done by enabling a feature for the crate.
2. 2.▲
   by bowlerman 4y ago

   That's the way it's resolved in languages with a standard, multiple compilers and no preference towards any of the compilers. This doesn't mean it has to be done this way in Rust. It seems like Rust is leaning towards doing t
3. 3.▲
   by bowlerman 4y ago

   > Maybe there needs to be a tiny (incomplete?) rust compiler. Or maybe there should be an interpreter. In which case the issue is "Rust doesn't have a small compiler" or "Rust doesn't have an interpreter". H
4. 4.▲
   by bowlerman 4y ago

   Having a standard is overrated. What you usually want is clearly defined behavior and a good backwards compat story. Standards only make sense to me in the presence of multiple compilers or formal verification. There is ongoing work on supp
5. 5.▲
   by bowlerman 4y ago

   Those qualifications are going to hold for any advice about technology. You can even justify using malbolge for your hobby project with "I like it" or "It's just for fun". If your company is only going to pay you fo