vscode extension updated to format nims and nimble too: 
<https://marketplace.visualstudio.com/items?itemName=arnetheduck.vscode-nph>

A few projects I know of that migrated to `nph` 0.5.1, in case you're curious 
about what it looks like in the wild:

  * [results](https://github.com/arnetheduck/nim-results)
  * [nlvm](https://github.com/arnetheduck/nlvm)
  * [fluffy](https://github.com/status-im/nimbus-eth1/pull/2020)
  * [nwaku](https://github.com/waku-org/nwaku/pull/2396) \- comes with a handy 
vscode [setup 
guide](https://github.com/waku-org/nwaku/blob/master/docs/contributors/nph.md)



Regarding lines between proc's, some like 1, some like 2 and some like 3 - this 
is something that you can spend endless cycles discussing - 1 was chosen in 
`nph` because that's what caused the smallest diff in the projects whose code I 
looked at when seeking a majority opinion that would lead to the smallest diff 
to how nim is used in the wild.

Reply via email to