dureuill

22 ms·

181.
by dureuill 5y ago
A subset of C++ cannot simultaneously be secure and useful, because to be secure a subset would need to ban pointers, references, iterators, moves and the ability to include code that is not part of this subset (for the last point modules m
182.
by dureuill 5y ago
I guess what the parent is saying is that, while the same kind of bugs can happen with signed integers, they are less common than with unsigned integers because they typically involve very big or very small values such as INT_MAX or INT_MIN
183.
by dureuill 5y ago
> Try and read a moderately complex Rust crate and it can be mind boggling to work out what is going on. I do that all the time, even reading the source of the std, something that I cannot do sanely in C++. IME Rust code is easy to read,
184.
by dureuill 5y ago
Yes, users can misuse warnings by ignoring them in CI, but the ergonomic cost of forcing unused variables as errors is disproportionate in regard to this. This affects all users regardless of if they would deny warnings in CI, and leads to
185.
by dureuill 5y ago
agreed. Rust has a warning for unused items, which is indeed interesting to catch logic errors (variables that should be used, but aren't). No need to fail compilation for this. It is then on you to deny warnings in CI to ensure that t
186.
by dureuill 5y ago
Thank you!
187.
by dureuill 5y ago
Would you happen to have some links about Linus hating Ada? While his stance on C++ is well-known, this is the first time that I hear he has public opinions about Ada. Thank you
188.
by dureuill 5y ago
I had some luck with yew + bulma.io. There's a crate called ybc they implements yew components using bulma classes. I had to reimplement a component myself though because I needed to hoist its state. Doing so wasn't very complicat
189.
by dureuill 5y ago
Well, a dedicated package manager such as cargo sure is convenient. Maybe what we currently need is rather a "meta package manager" that knows of many package managers and can orchestrate them?
190.
by dureuill 5y ago
While it is technically not 1.0, I have yet to see a breakage and I have been using it since 0.7. The language maturity one, I can concur though. The rust implementation has been fine, but pycapnp was plagued with memory leaks until recentl