Jacek Sieka

Indeed, or a nimble package that could follow a separate release cycle and prove is utility there..

We seem to keep coming back to this topic, that the standard library is a place where code goes to die without there being an process for cleaning up the...

> [09:32] Varriount: @arnetheduck I really liked your comment regarding standard library versioning. I think, when it comes down to it, package management is an inevitable need. > How would...

> Not reviewed, using different styles and of different code qualities with different attitudes towards backwards compatibility. This is probably the point that's misunderstood the most in these discussions -...

> To put it differently, would we recommend a new Nimble package to be published every major version release ? absolutely not - the whole point is to _not_ have...

> I'm sure, I'm not the only one in the Rust community who would absolutely love to use Nim and leverage the Rust ecosystem. See also https://github.com/arnetheduck/nbindgen/ - this is...

https://github.com/status-im/nim-chronos/blob/9186950e03254b87533715f7c991a537b3167bef/chronos/apps/http/httpserver.nim#L261

Indeed, fixing this will require persisting the aristo txframe snapshot to disk.. however, it's certainly unusual that F is not updating for this long, even in LC mode.

bumped to fix breakage - ping @Cuteivist @IvanBelyakoff @endulab

> Please don't merge master in your PR, just rebase your commits on top my understanding from the repo history is you `git merge --squash` them, which has the same...