some (like @wycats) think so
-
-
string paths seem reprehensible to me but I think there's a middle ground
-
I most put it forth as a straw man to illustrate that "thinking in paths" 1/
-
is easier for humans -- I'd be very open to other options, but I disagree 2/
-
that `use self::foo::bar` is "magic" any more than ES6 syntax is. 3/3
End of conversation
New conversation -
-
-
I think we think in langs we know; I find this more confusing than mod ;)
-
first glance" is not the thing to check -- it's whether ppl find it 2/
-
confusing *once they learn it* -- Rust's mod system is confusing 3/
-
*after people learn it*, while ES6's in practice is not after people do 4/4
-
i guess. it's pretty much always made perfect sense to me.
-
you found extern crate + mod + use + self + super to be straight forward? 1/
-
especially the part where `mod` paths and `use` paths are different? 2/2
-
... done. "self" and "super" fall out of "use starts from the root." and shouldn't be used anyway imho.
- 7 more replies
New conversation -
-
-
ah yeah, ok i get this. tho this line is a lil odd https://gist.github.com/wycats/7c3de08ac320901d29140378d98b0561#file-3-my-mod-rs-L5 …
-
the way Node does it, where everything is public, doesn't work for Rust. 1/
-
I think it's nice to be able to hide things from the module system :P 2/2
End of conversation
New conversation -
-
-
(I have always been weird in liking the module system though. sigh.)
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.