See also the horribly un-discoverable (PR welcome) but occasionally life safer
`patchFile`, which can work without having to mess with source files.
I have some ideas how to make `patchFile` work even better, by patching at the
AST level (using macros) instead of at the source code level
Thanks. I'll try that.
I usually use the git folder to upgrade my Nim installation. This allows me to
have my own changes (in a patch file or a branch/commits). Then I can just
apply the patch or rebase on top of a new release.
Just upgraded to Nim 1.4.0 using choosenim and it was fairly painless, but I
was wondering what the best way of handling customisations, for example changes
to nim.cfg and any changes to nim files in the lib folder.
Obviously I can keep a note of my changes and re-apply them after upgrading,
bu
