News for hackers. Stuff that matters.

A comment on Comparing the Same Project in Rust, Haskell, C++, Python, Scala and OCaml. Parent comment

Re:Comparing the Same Project in Rust, Haskell, C++, Python,... by k_bx on Sunday June 16, 2019 @06:12AM (#20194785)
I disagree about lens. My new projects don't use them in main code-base and it was a great decision:

- TAGS work like a charm to access field definitions

- compile times are ok

Of course, if library's API needs lens, they're used.

[ Parent | on HN ]
Re:Comparing the Same Project in Rust, Haskell, C++, Python,... by exceptione on Sunday June 16, 2019 @10:39AM (#20195668)
What do you mean with TAGS?
[ Parent | on HN ]
Re:Comparing the Same Project in Rust, Haskell, C++, Python,... by k_bx on Monday June 17, 2019 @08:37AM (#20202253)
File named TAGS generated from hasktags (in case of Haskell) that gives you an easy way to "jump to definition" from Emacs or other editors. Good way to navigate codebases even if you don't know how to build them.
[ Parent | on HN ]
Re:Comparing the Same Project in Rust, Haskell, C++, Python,... by sanityinc on Monday June 17, 2019 @02:22AM (#20200376)
Presumably etags/gtags/hasktags etc., ie. having built a TAGS database for such a helper program, you can use it in an editor to jump from a field name to its definition. That wouldn't be the case with a lens accessor.
[ Parent | on HN ]