4 ms·
RE the point about catching mistakes involving far apart pieces of code, they are clear that it's "interprocedural", so the analysis is only within a single fun
by drewm1980 4y ago
RE the point about catching mistakes involving far apart pieces of code, they are clear that it's "interprocedural", so the analysis is only within a single function at a time. Like with rust, there is a focus on annotating function inputs and outputs, with a lot of inference within functions. I am curious if there's a way to quantify how quickly the safety propagates as you do gradual typing. If you annotate 20% of the functions in a typical codebase, does 90% of the runtime data pass through an annotated function boundary at some point, catching 95% of the ownership bugs?
- fedux 4y agoIt's intraprocedural.
- drewm1980 4y agoIndeed. Embarrassing! I consciously avoid using "intra" or "inter" in English for this reason, and when I do because of someone else's jargon I also say what I mean to disambiguate. Unfortunately we can't deprecate english to avoid these mistakes... but maybe we can design a system of macros we can insert into our posts to statically check if our usage is correct.
- ttfkam 4y agoI always think of "international" as the baseline, because I know it means among multiple nations. Intra- is "the other one". Also, isn't "inter-" vs "intra-" a Latin idiom? It's present in all Romance languages. English got it through French. Luckily I think this is an area where tools like ChatGPT (and modern word processor tech) can help us all out.