This Week in Rust(cmr.github.io)
cmr.github.io
This Week in Rust
http://cmr.github.io/blog/2014/02/09/this-week-in-rust/
4 comments
Here's one that's been on my mind that I haven't seen people talk about: making O(1) and O(n) operations look the same.
Example in Python:
I think a lot of the problem is the subtle syntax. People with a solid CS background find this distinction fairly natural, but most Python programmers apparently don't.
I guess the alternative syntax would be L.find(), which sort of emphasize the linear search. It seems WAY more elegant to have the polymorphic "in", but the number of mistakes is too high.
Actually now that I think about it, this was question #0 on the stripe CTF3. So I guess the same thing happens often enough in Ruby for them to use it as a question.
Example in Python:
d = { ... }
for ...
if 'key' in d:
func()
L = [ ... ]
for ...
if 'key' in L:
func()
I think a lot of the problem is the subtle syntax. People with a solid CS background find this distinction fairly natural, but most Python programmers apparently don't.
I guess the alternative syntax would be L.find(), which sort of emphasize the linear search. It seems WAY more elegant to have the polymorphic "in", but the number of mistakes is too high.
Actually now that I think about it, this was question #0 on the stripe CTF3. So I guess the same thing happens often enough in Ruby for them to use it as a question.
I see this as ultimately being a much better from an optimization standpoint. Now I can change L to a set or a linked list if I find that more efficient without having to change it everywhere. Language features are no substitute for algorithm and data structure knowledge, which your students can likely be forgiven for not knowing about.
I don't buy it. Physically editing text is never the problem when changing a data structure like this. The work is ensuring your program is still correct and performs better.
Ensuring code is "still correct and performs better" is made easier if only the data structure used has to change to get "performs better", and the "still correct" comes free with it because the operation that performs the same function is the same operation regardless of the efficiency of the algorithm.
Right. And this kind of polymorphism means that your program will still retain the same correctness no matter what data structure you use. Physically editing text is the most correctness-destroying thing you can do.
It sounds to me like you know enough to write such a book. ;-)
I'd certainly like to read such a thin.g.
I'd certainly like to read such a thin.g.
As some of the Rust developers hang around here, a question:
Result is the Either monad in Scala / Haskell? So IO functions return either a success wrapping a value, or a failure? This is great -- I'm a big fan of this style of error handling. However it seems that Rust doesn't have syntax for monads -- the equivalent of Haskell's do and Scala's for. This makes monads a bit of a PITA. Is there a plan to address this?
Result is the Either monad in Scala / Haskell? So IO functions return either a success wrapping a value, or a failure? This is great -- I'm a big fan of this style of error handling. However it seems that Rust doesn't have syntax for monads -- the equivalent of Haskell's do and Scala's for. This makes monads a bit of a PITA. Is there a plan to address this?
People keep wanting monadic syntax (I'm one of them), but I believe the general suggestion is to do it via macros/syntax extensions. E.g. write something that desugars
Also, note the `if_ok!` macro alluded to in the point about IO errors is giving the shortcircuiting behaviour of the Either monad (specific to Either, though).
(NB. the macro probably can't be called `do` just yet, but we may remove that as a keyword. Maybe.)
do! {
bind x = foo();
let bar = baz(10);
ret x + bar
}
do
x <- foo
let bar = baz 10
return $ x + bar
Also, note the `if_ok!` macro alluded to in the point about IO errors is giving the shortcircuiting behaviour of the Either monad (specific to Either, though).
(NB. the macro probably can't be called `do` just yet, but we may remove that as a keyword. Maybe.)
Wait, how don't macro need to take escaped sigils?
Like range! takes range!('[' 0 , Inf ')' )?
Is 'do' still a keyword? I remember it being removed, pretty much everywhere. I just assumed it was thrown away.
Like range! takes range!('[' 0 , Inf ')' )?
Is 'do' still a keyword? I remember it being removed, pretty much everywhere. I just assumed it was thrown away.
They need to take balanced braces/parens/brackets (i.e. only escaped if they are possibly unbalanced), so that Rust source can still be parsed without having to run the macro expander concurrently.
And, it looks like do is no longer a keyword at all, I must've missed that part of the do-removal patch! So it is possible to call that macro do.
And, it looks like do is no longer a keyword at all, I must've missed that part of the do-removal patch! So it is possible to call that macro do.
> Wait, how don't macro need to take escaped sigils?
These are proper (hygienic) syntax macros, much like Scheme's syntax-rules. C's "macros" only work at the token level.
> Is 'do' still a keyword?
I believe it is still a reserved keyword, but not used anymore.
These are proper (hygienic) syntax macros, much like Scheme's syntax-rules. C's "macros" only work at the token level.
> Is 'do' still a keyword?
I believe it is still a reserved keyword, but not used anymore.
As Rust ML lurker - there was some talk about using macros to fill in for this pain point, if I recall correctly. From what I've gathered do is dead and gone.
For anyone not familiar with it, the `do` that was removed provided sugar for calling HOFs similar to Ruby blocks.
Monadic do could be added in the future, backwards compatibly.
Monadic do could be added in the future, backwards compatibly.
"if_ok!" is designed to handle this. It's basically the equivalent of monadic do, but works better with the control flow structures of Rust.
Is there a location in the docs that lists and describes the built-in macros in Rust? They don't appear to be findable using the stdlib search, and the Macros tutorial doesn't seem to talk about built-ins.
Also, this post forced me to read the docs a bit more thoroughly and realize that I haven't been distinguishing between Option and Result. Thanks
Also, this post forced me to read the docs a bit more thoroughly and realize that I haven't been distinguishing between Option and Result. Thanks
I noticed that rustpkg has been removed, leaving Rust essentially without an official package manager for the time being. Can't say I'm heartbroken, but what's the plan?
> Rust is a systems language pursuing the trifecta: safe, concurrent, and fast.
> It was also discovered that we closed the second largest number of issues of any repository on GitHub!
Doesn't make me very confident...
> It was also discovered that we closed the second largest number of issues of any repository on GitHub!
Doesn't make me very confident...
>Doesn't make me very confident...
This makes no sense at all. For one, it's a language under heavy development. Obviously most of these issues where things not implemented already, library ftuff missing, temporary implementations that had to be changed to the new one, small and bigger regressions due to syntax and library changes etc etc.
Second, you'd rather those issues remained open? Or that magically some rainbow unicorns perhaps would have prevented the language from having any issues in the first place?
What matters is that the number of issues drops low enough, as the language tries to reach version 1.0. And what the announce here is very well aligned with that goal.
This makes no sense at all. For one, it's a language under heavy development. Obviously most of these issues where things not implemented already, library ftuff missing, temporary implementations that had to be changed to the new one, small and bigger regressions due to syntax and library changes etc etc.
Second, you'd rather those issues remained open? Or that magically some rainbow unicorns perhaps would have prevented the language from having any issues in the first place?
What matters is that the number of issues drops low enough, as the language tries to reach version 1.0. And what the announce here is very well aligned with that goal.
There's no need to be snide.
I think he may just be surprised that those bugs still occurred, given how the Rust toolchain is itself implemented in Rust, by the designers of Rust, and how Rust is supposedly designed in a way that prevents bugs to a larger extent than other languages do.
It's understandable where he's coming from. If those who know Rust the best are still subject to bugs in their Rust code, it's perfectly valid and reasonable to wonder if the rest of us really be any better off than we are with Java, or C#, or Python, or whatever language(s) we're currently using.
I think he may just be surprised that those bugs still occurred, given how the Rust toolchain is itself implemented in Rust, by the designers of Rust, and how Rust is supposedly designed in a way that prevents bugs to a larger extent than other languages do.
It's understandable where he's coming from. If those who know Rust the best are still subject to bugs in their Rust code, it's perfectly valid and reasonable to wonder if the rest of us really be any better off than we are with Java, or C#, or Python, or whatever language(s) we're currently using.
>I think he may just be surprised that those bugs still occurred, given how the Rust toolchain is itself implemented in Rust, by the designers of Rust, and how Rust is supposedly designed in a way that prevents bugs to a larger extent than other languages do.
Well, then what he probably doesn't understand is that those bugs are not in their majority memory bugs or sound-ness bugs or bugs in the things Rust is supposed to protect you from.
Most are issues related to half or mis-implemented features, syntax that changed and libs that need to change in accordance, etc. If I have:
random() { return 6;}
as a stub, I could post an issue to remind me to implement a actual random number generator later. Doesn't mean the language has some inherent problem itself.
Well, then what he probably doesn't understand is that those bugs are not in their majority memory bugs or sound-ness bugs or bugs in the things Rust is supposed to protect you from.
Most are issues related to half or mis-implemented features, syntax that changed and libs that need to change in accordance, etc. If I have:
random() { return 6;}
as a stub, I could post an issue to remind me to implement a actual random number generator later. Doesn't mean the language has some inherent problem itself.
A lot of the issues included in that count are pull requests (including ones adding awesome new features, not just fixing bugs), and we get a reasonable number of duplicate filings (which doesn't particularly matter: it gives us more test code for the suite).
Pursuing != is.
Its a language in the stages of infancy and under active development, of course there are bugs. Its not even at version 1.0 yet!
Its a language in the stages of infancy and under active development, of course there are bugs. Its not even at version 1.0 yet!
So would you be more confident in repositories that closed 0 issues? I can point you to plenty of those.
Issues are not bugs just because bugs happen to be issues. Depending on development workflow every contribution might be made as a pull request and therefore show up as an issue. Also most projects tend to underreport issues, in that a lot of bugs are fixed or features implemented without creating an issue.
You can easily achieve a high number of issues compared to other projects, just due to workflow and by using issues heavily to document what you are doing.
What would be concerning is a large number of old open issues or if the number of opened issue is significantly larger than the number of issues being closed.
You can easily achieve a high number of issues compared to other projects, just due to workflow and by using issues heavily to document what you are doing.
What would be concerning is a large number of old open issues or if the number of opened issue is significantly larger than the number of issues being closed.
While working for a Smalltalk vendor, I got to see that the various Smalltalk implementations all made the same mistakes. (Visualworks, ObjectStudio, Digitalk) Then later on, I've seen eerie reminders of those things I saw in other environments/languages.
This is a highly complex subject, not only spanning a great deal of technical material, but also interactions within communities of many programmers, decision makers, and others.
I think such a book would be highly valuable to the programming field. (Or, as Alan Kay says, "not quite a field.")