phaylon

10 ms·

31.
by phaylon 8y ago
And they want your phone number :)
32.
by phaylon 8y ago
> It's not a misconception, there are plenty of times in the past year that I've heard someone propose some change for the new edition only for the Rust devs to meet it with "that's not possible because we can't
33.
by phaylon 8y ago
Personally I wish it wouldn't have to be a fight, but Github issues are not well suited for large scale design discussions and are bound to produce certain amounts of grief.
34.
by phaylon 8y ago
I'd consider that a misconception. Everything that can be deprecated can be removed and replaced by a new edition. See the discussion here: https://www.reddit.com/r/rust/comments/82sxxf/epoch_vs_era_
35.
by phaylon 8y ago
I made a bit of a list of the big ones here: https://news.ycombinator.com/item?id=16837894 The interesting (and to me frustrating) part is that often good improvements (or intentions to solve actual problems) come together
36.
by phaylon 8y ago
I'd say there are a couple of things that apply: * `?` can propagate values/short circuit control flow, but it also contains a hidden type conversion. The target needs to be a known type for it to compile. * A proposed `catch` con
37.
by phaylon 8y ago
I'd say Rust's first line of solutions for this is macro_rules. They are structured, allow common patterns to be re-used in various places, can be reviewed and maintained in one place and apply to all uses, they can even be distri
38.
by phaylon 8y ago
I was part of a couple ergonomics discussions and I disagree. Yes, in the end the changes don't sacrifice long-term maintainability over learnability/marketing, but that was a hard fight. And given editions will allow radical chan
39.
by phaylon 9y ago
Almost 9 years for me without downvoting.
40.
by phaylon 9y ago
At this point, I have basically given up on the extensions I care about working correctly in the future. These addons (tree style tabs, tab open/close control) already have webextension versions, but are extremely buggy for me, and I b
41.
by phaylon 9y ago
Well, if we're having some bike-shedding fun: let (a, b) = c[..16..];
42.
by phaylon 9y ago
> I don't think you need a good understanding of C++ to appreciate these features per-se. Only if you want to make a statement like "X is an improvement over C++ because of these". What about "X encoding thread-safety
43.
by phaylon 9y ago
The big safety wins from Rust for me are things like the type system disallowing iterator invalidation, the type system handling resource releases, iterators making bounds checks a lot more affordable, the shared immutable/unique mutab
44.
by phaylon 9y ago
I'm not sure what you mean. Can you give an example?
45.
by phaylon 9y ago
You can implement traits for both kinds of references, so a function might accept both.
46.
by phaylon 9y ago
The Real Life Webcomic has (or had, years ago) quite a share of storylines about the advantages of that :)
47.
by phaylon 9y ago
The question I always ask is: If it were not "scan, destruction, reconstruction" but just "scan, reconstruction" and you end up with two identical you's first, would you be fine with simply being killed then? Inspir
48.
by phaylon 9y ago
At least for posts, on discourse forums I see a control on the right where I can go to specific posts. It's useful because it also shows you what date you are jumping to.
49.
by phaylon 9y ago
By "public marketing effort" do you mean "people talking about Rust"? Personally, I interpret the focus on memory safety as a response to "memory issues aren't a big deal" or "memory issues only come
50.
by phaylon 9y ago
I'm only lurking on the D forums, so this should probably be taken with a grain of salt. From what I understand the GC is required for various array, hash map and string operations, and things like closures and exceptions (maybe assert
51.
by phaylon 10y ago
I would assume LTS and rolling releases align for some people due to impact on the user. LTS gives a long time between impacts, rolling releases spread the impact out over time. I could see every-n-months releases to hit a bad spot of too f
52.
by phaylon 10y ago
The D forums seem to suggest this is only true for primitive types, is that correct?
53.
by phaylon 10y ago
Well, from my outside perspective there are certainly "Lack of generics is a feature" and "Generics are a feature that has not yet arrived" camps. Again from an outside perspective, it also seems that these camps talk ab
54.
by phaylon 10y ago
Yes, but I didn't understand the implications or background. If the prerequisite for having enough basic knowledge is "making it halfway through a C tutorial" it doesn't seem as much of a hindrance as your top comment su
55.
by phaylon 10y ago
No, I _tried_ and failed. I've never made it anywhere close to writing my own C or C++ code, and failed at the tutorial stage or earlier.
56.
by phaylon 10y ago
I feel that that's not really true. I'm from a dynamic language background and I didn't have many problems. Quite the opposite actually, as to me the Rust compiler was more of a teacher at first. I've tried getting into
57.
by phaylon 10y ago
> My reading is that most of the problems come from a lack of manpower or perhaps a lack of delegation but I'm only reading this as an outsider. Preface: I don't use D, but I've lurked on the forums for a while now since I
58.
by phaylon 10y ago
Maybe 'collapse' and 'expand' would be good substitutes for the '-' and '+' at the top?
59.
by phaylon 11y ago
I'm actually very glad to hear that. I've been working on (read: designing, not yet implementing) a GUI framework for Rust, and was hoping to get away without an external 2D rendering library like cairo. And if CSS can be reduced
60.
by phaylon 11y ago
There's also the group of people I'm in: I _like_ the explicit semicolons.

More ›