4 ms·

well, yes, that's why nimgrep exists. grep -i solves the case issue, and grep/ripgrep probably _should_ have a feature to ignore _ ; in which case you will be

well, yes, that's why nimgrep exists. grep -i solves the case issue, and grep/ripgrep probably _should_ have a feature to ignore _ ; in which case you will be able to use them - but until then, nimgrep will do that work.

tcoff91 8y ago
It seems crazy to me that people are so annoyed that their libraries have different style that we have to have additional tooling to make code search simple for the end-user.
- dom96 8y ago
  You don't _need_ additional tooling. You can get by with just searching as normal, it's not as if people's code bases are filled with random conventions or random case variations...
  - tcoff91 8y ago
    style insensitivity WILL lead to typos that don't get caught. Someone will change the casing somewhere. Therefore you must always search with style insensitivity in mind.
    - nimmer 8y ago
      Most people use completion anyways and it prevents this problem. Also, you can lint the code.
- beagle3 8y ago
  Styles are religions, including - in some organizations - the threat of excommunication if you don’t practice the one style. I don’t know how atheistic style looks, but Nim is style agnostic - everyone can practice their religion and they all get along. C, Python, and the real world - not so much.