> The best ghc bug ever involved a dev version of the compiler deleting your source file if it contained a type error.
This sounds like the opposite idea, remove the function instead of repairing it. Very aggressive idea.
> I would be interested in the technique you used to do this. specifically, how did you get your code to kick off and check on module load?
Powershell has great error-handling, and all errors are stored in the special $Error variable. For missing commas, semicolons, brackets, and other punctuation, the errors usually have the line-and-column of the missing item.
So the function would just parse $Error and update the module file with the right item at the right location.
Aw, Terry's YouTube channel was taken down. He did so many walkthroughs of HolyC and his dynamic programming engine.
Oh well, 353 videos were archived at least.
Thank goodness for archive.org!
Flight simulator: https://ia801506.us.archive.org/2/items/TerryADavisTempleOSY...
Due to copyright strikes not all content was available for download.
Sounds like copyright strikes. He had 1,140 videos uploaded. That's like burning down a library.
I'd guess if he streamed on Youtube, his account is terminated so that's no longer possible.
I kind of want to go through the legwork of reuploading most of the 1100 videos and then giving Terry the username+password of the new channel. But I don't know if that will run afoul of Youtube's policies and I don't want to be banned for life myself.
(Archive.org snagged most of the 1100 videos, not just ~300. But some of them are just missing.)
There's a proposition to not only delete the code but commit and push the git repo its a part of.
The proposal goes further...
There is no free will, assents the officer; We hang because we must.”
It's not obvious who's to blame here, the caller or the callee.
Well, that's because it is irresponsible.
That adds a level of terror... Maybe somebody will add it to a tech interview. I mean, it's got a Debian package.
assert n >= 0
assert result >= 0
Also, implore specifies the caller is offensive, and any function which swears a falsehood is offensive. The latter is like assert, but the former is like lifting the assert to the caller.
Referential self-punishment. Self-removing code during runtime based on a predestined moral functor.