Is this somehow concatenated together in a build process, or is it actually written and maintained like that?
Originally it was written in lisp then translated using a tool. But I believe it's maintained like that.
I think this lisp part was in this talk, but I'm not 100% sure what he did say
"I'm not 100% sure what he did say" - this makes me a little worries. What wasn't clear exactly? I've hoped that the GC history from 48:50 covered "the Lisp part" good enough.
I've been jumping through video to see what is this about and heard something about lisp2cpp transpilation myth (that I've heard before)
It's not related to your english, ability to express or something.
Anyway, thanks for the effort
Re:.NET GC Internals mini-series
by throwaway189262 on Saturday January 23, 2021 @07:31AM
(#25881760)
Lol this might be a common thing in MS language projects. I heard the Typescript compiler is also a single notoriously large file
Re:.NET GC Internals mini-series
by gameswithgo on Saturday January 23, 2021 @08:22AM
(#25882009)
When you get into more "low level" domains, huge single files are more common. Some feel there is a correctness justification, being able to follow the code from top to bottom rather than jumping around, see: http://number-none.com/blow/blog/programming/2014/09/26/carm...
Personally I think it just doesn't matter. 50k lines of code is 50k lines of code. Whether it is in one file or 10 or 100, only changes whether you jump around via a file tree or other editor tools.
There are some practical problems when you get too huge though, like not being able to view the thing in github!
https://raw.githubusercontent.com/dotnet/runtime/master/src/...