News for hackers. Stuff that matters.

A comment on A Farewell to FRP. Parent comment

Re:A Farewell to FRP by swaroop on Tuesday May 10, 2016 @02:46PM (#11669557)
The new C++ Core Guidelines & Guidelines Support Library and related tools are interesting efforts to specifically solve those problems.
[ Parent | on HN ]
Re:A Farewell to FRP by Buttons840 on Tuesday May 10, 2016 @03:35PM (#11669943)
If the issue is that "C++ compiles stuff that may or may not work at all" then I don't see how those guidelines will help the situation. A C++ project may or may not follow those guidelines and then we're back where we started.
[ Parent | on HN ]
Re:A Farewell to FRP by swaroop on Tuesday May 10, 2016 @05:24PM (#11670785)
My understanding is that the tools are the answer - it's a linter that must be run before landing/merging. See https://youtu.be/hEx5DNLWGgA for a demo of such tools.
[ Parent | on HN ]
Re:A Farewell to FRP by bjz_ on Wednesday May 11, 2016 @08:31AM (#11674636)
Tools are just band-aids over an unsafe type system, and they are all too easy to ignore or never use them in the first place.
[ Parent | on HN ]
Re:A Farewell to FRP by swaroop on Wednesday May 11, 2016 @11:37AM (#11676253)
It depends on the community. See gofmt & gometalinter in the golang community.
[ Parent | on HN ]