Show HN: Sourcetrail – Get productive on unfamiliar source code

Re:Show HN: Sourcetrail – Get productive on unfamiliar sourc... by dkarapetyan on Thursday June 22, 2017 @02:43PM (#14614353)

As noted by others the annotations would be active checks. More like proofs in coq than static text. That way you'd be building up a logical understanding of the code base that was machine verifiable sidestepping the issue of stale comments.

If done properly this could even feed into code dynamics to capture information on the runtime information. So that at every point in the program you could start asking questions like how many times did this line execute, what was the type of this variable at this point, how much memory was allocated, and so on and so forth.

[ Parent | on HN ]

Re:Show HN: Sourcetrail – Get productive on unfamiliar sourc... by nautilus12 on Tuesday June 27, 2017 @07:50AM (#14644466)

Seems like youve just abstracted things like static typing into a extension of the language thats checked at a less optimal time. At this point arent you better off just using a language that incorporates this functionality and compiles it? Sounds like youve just implemented static typing but in a really akward and unecessary way

[ Parent | on HN ]