xialvjun

@daanx Hope you fix this before it's too late.

I don't know why "no path based imports" may be a disaster. Things should be simple. We can access: ``` sibling sibling's public children sibling's public children's public children... ancestor...

It seems `use` and `mod` is just sugar of `const`, and dependency list is just top module ``` // Cargo.toml [dependency] tokio=0.1.0 hyper=0.2.0 // In src/main.rs // dependency list is...

My question in short: how to declare something public in its library but private out of its library.

Some use case: I have a library like ffmpeg for av processing, and I need some tool functions in it, those tool functions are only used by myself in this...

Zero argument anonymous function koka: ```koka fun printhi10() repeat(10) { println("hi") } ``` or: ```koka fun printhi10() { repeat(10) { println("hi") } } ``` js with arrow syntax: ```js function...

@gaearon just like [this](https://github.com/facebook/react/issues/16728#issuecomment-664913171) comment, I filed a new issue. And in this issue, I gave a real use case, hoping this will draw you guys' attention.

Although react lifecycle order works right, it lacks `componentDidUnmounted`. Related issue: https://github.com/facebook/react/issues/6424 . This issue is closed because > Closing as React's design is moving away from class-based lifecycle methods...

To solve the problem of **parent component can not clean up resource shared by its children**, there is a hack way: https://github.com/facebook/react/issues/6424#issuecomment-351760732 And by imitating the above method I wrote...

If useing `setTimeout`, what about parent's parent?