Twitter | Pretraživanje | |
Patrick Walton 30. sij
Easy to say "monomorphization is awful and Rust should never have done it", harder to say "I want all generic functions to be compiled to bytecode and to embed a Rust interpreter in every binary".
Reply Retweet Označi sa "sviđa mi se"
Patrick Walton
I'm increasingly convinced that the interpreter solution is the only reasonable alternative for Rust.
Reply Retweet Označi sa "sviđa mi se" More
Patrick Walton 30. sij
Odgovor korisniku/ci @pcwalton
*I'm* actually OK with this as an opt-in compilation mode, at least for cold functions. But are the people complaining about compilation time OK with it?
Reply Retweet Označi sa "sviđa mi se"
Watson Ladd 31. sij
Odgovor korisniku/ci @pcwalton
Wait, why doesnt ML gave this problem?
Reply Retweet Označi sa "sviđa mi se"
Patrick Walton 31. sij
Odgovor korisniku/ci @WatsonLadd
Uniform value representation. Traditionally, all values in MLs are one hardware word. This simplifies things a lot.
Reply Retweet Označi sa "sviđa mi se"
knights who say nikolai 31. sij
Odgovor korisniku/ci @pcwalton
Have you considered what Swift does with generating vtables for the functionality required by the generic function?
Reply Retweet Označi sa "sviđa mi se"
Patrick Walton 31. sij
Odgovor korisniku/ci @NikolaiVazquez
Yes, see other replies
Reply Retweet Označi sa "sviđa mi se"
Benjamin Smedberg 30. sij
Odgovor korisniku/ci @pcwalton
I would love an interpreted rust with a fast dev cycle!
Reply Retweet Označi sa "sviđa mi se"
Patrick Walton 30. sij
Odgovor korisniku/ci @nsIAnswers
Me too!
Reply Retweet Označi sa "sviđa mi se"
Chad Austin 31. sij
Odgovor korisniku/ci @pcwalton
Is there a GHC-like middle ground where all generic values are boxed?
Reply Retweet Označi sa "sviđa mi se"
Ben Karel 31. sij
Odgovor korisniku/ci @pcwalton
If you can find the cycles to spare, laying out the constraints/reasons involved could make for a very interesting blog post!
Reply Retweet Označi sa "sviđa mi se"