While I am only a Rust novice it seems to me like the "2.2 Item 11: Implement the Drop trait for RAII patterns" could use some kind of mention of Drop-leaks. I learned about it at https://doc.rust-lang.org/nightly/nomicon/leaking.html
Same thing for the "Product Brief" document that maybe goes into detail about the hardware.
The Media section does have some details such as whitepapers and a doctoral thesis. Still it would be nice to have specifications for the actual product if you are trying to sell it...
The git history is useful to find out:
* The why, who and when of some change to the code or configuration.
* Looking at older variants of code to see previous attempts to know what has already been tried.
* git blame and git bisect for automated troubleshooting.
While I do not build LFS regularly or for production use, the security improvement typically comes from the fact that the end system is _super_small_ and focused. Less software means less attack surface.
Sure, compromised binaries are nasty but personally I do place quite a lot of trust with the distribution repos.
(PS, if you are reading this and contribute packages to distribution repos: Thank you!)
Ah yes, the dreaded page limit! I look for examples of working synthesis so I will still read it.
The question of fixed vs. infinite integers and observable sizes of datastructures is a dilemma that I do not know of any good solution to. Selecting fixed and observable sizes leads to efficient execution but risks making programs unportable (after they have been compiled and are distributed as object code).
Selecting arbitrary precision integers and no observable sizes instead requires a smart runtime/jit/compiler to get efficient execution.
Nice work, I will have to read the research paper later ("Tacit Programming Code Synthesis and Optimization with Genetic Algorithms").
One question, why did you decide to make the size of cells visible to programs (pointer arithetic)?
Will that not lead to the same portability challenges that we have already had with C and C++?
Yes, `rot` is a higher order function that expects a function argument and returns another function as the result. In Scheme the car does not have to be a name.
> (3b) you could also build an ARCHIVE FILE (a statically linked library, libmylib.a) from one or more .o files. If you link with a static library, its code is copied into the a.out file at runtime.
Huh? There is no copying at runtime when using a static library.
Or have I misunderstood this all these years?
https://github.com/QUVA-Lab/escnn/pull/113#issuecomment-3892...
https://crabby-rathbun.github.io/mjrathbun-website/blog/post...