Timothee Cour

@dom96 IMO https://github.com/nim-lang/RFCs/issues/291 gives the missing ingredient to allow this RFC. Under this RFC, you'll have: * no scope pollution, which is a real problem * no need for `srcDir`...

> I really wish you would just use import jester. that's to avoid symbol clashes (cf rationale why std and pkg were introduced) related: this is how it's done in...

* does nimble (not necessarily published nimble pkg but for a local one) enforce that a pkg foo doesn't clash with an existing module in stdlib? eg would it error...

=> [programmatically prevent a package to be published that could clash with a stdlib module · Issue #576 · nim-lang/nimble](https://github.com/nim-lang/nimble/issues/576)

> We can make it optional though. yes! that's a clear violation of DRY otherwise (remembering to git tag on version bump in the nimble file), and leads to problems...

We should allow users to change the title, and there should be no time restriction. Github issues can have their titles changed at any time, and I'm yet to see...

unrelated (nothing to do with auth, despite the example using `username, password`); I'll try to explain better in a bit

Here's an example adapted from my code: ```nim # this is an existing API that takes regular Nim types and that we want to expose over the server proc postExtractFilePattern(input:...

> It seems like it would be very flaky. if it becomes too flaky we can simply add: ``` bash: testament cat nimble-packages ``` => ``` bash: testament cat nimble-packages...

it wouldn't block anything because of the `|| echo "FAILED (allowing failure)"` which causes it to never fail; if by block you mean "takes too long" (in practice should take...