I think we can get rid of both mod and extern crate. mod is worse.
-
-
but how do you control mod privacy without mod
1 reply 0 retweets 1 like -
Replying to @withoutboats @ag_dubs and
with explicit exports (basically pub mod).
2 replies 0 retweets 0 likes -
i guess we could use `pub use self::submodule` instead?
2 replies 0 retweets 2 likes -
Replying to @withoutboats @wycats and
its not clear to me that mod makes something public
1 reply 0 retweets 0 likes -
it doesn't (pub mod does!)
2 replies 0 retweets 3 likes -
Replying to @withoutboats @ag_dubs and
you build your tree with mod & then you import from it with use
4 replies 0 retweets 2 likes -
Replying to @withoutboats @wycats and
ah yeah, building a tree is the step that loses me
1 reply 0 retweets 1 like -
Replying to @ag_dubs @withoutboats and
this is what I mean: https://gist.github.com/wycats/7c3de08ac320901d29140378d98b0561 …
4 replies 0 retweets 1 like -
string paths seem reprehensible to me but I think there's a middle ground
1 reply 0 retweets 1 like
I most put it forth as a straw man to illustrate that "thinking in paths" 1/
-
-
Replying to @wycats @withoutboats and
is easier for humans -- I'd be very open to other options, but I disagree 2/
1 reply 0 retweets 1 like -
Replying to @wycats @withoutboats and
that `use self::foo::bar` is "magic" any more than ES6 syntax is. 3/3
0 replies 0 retweets 0 likes
End of conversation
New conversation -
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.