4 ms·
Main reason for this feature is that Nim is big as a glue language. Many C/C++ libraries don't have consistent naming conventions between them. I don't want my
by treeform 7y ago
Main reason for this feature is that Nim is big as a glue language. Many C/C++ libraries don't have consistent naming conventions between them. I don't want my code to look like a patch work of `__APICALL__(system_call.inspectSomething())` I just want it to look like Nim code: `apiCall(systemCall.inspectSomething())`. This is just a consistent standard on how to turn names in one style into another style backed into a language.
- airstrike 7y agoapiCall = __APICALL__ done
- treeform 7y agoThen you are writing or auto generating these giant 1000s of lines long files with renames... why?
- airstrike 7y agoI never said it was a good idea!
- beagle3 7y agoSo you are writing hundreds of rename rules. Well, unlike treeform, I like it to be: api_call(system_call.inspect_something()) Which I find much more readable. What now?
- deleted 7y ago[deleted]