Vigil comes from Munificent, the principle developer of wren, an unironic language that fills lua's niche (portable c, embeddable, no dependencies), with a nicer syntax: https://github.com/munificent/wren
I believe he is also on the Dart lang team at google. He has a pretty awesome blog and is super insightful when it comes to programming languages. His Github projects inspired me to research language design further.
Yep his blog and books are great. Incidentally I started looking into Dart yesterday. Seems like a comfy language, more so than Typescript in my opinion.
I made an automatic error fixer once in Powershell. When you load a module, it would catch missing commas between parameters, and update the module file with the missing commas. I want to extend it to catch many more common coding mistakes.
This sounds like the opposite idea, remove the function instead of repairing it. Very aggressive idea.
Replying to braveo's unfortunately dead comment[0]:
> 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.
Jokes aside, semantically "implore" and "swear" are actually really good primitives for static analysis. "swear" is only dangerous because there's a chance it gets out of sync with the code it's swearing for.
Check out Eiffel if you want a serious version of pre/post conditions and invariants. Or any number of functional languages where the approach tends to be to use the type system for these type of guarantees instead.
I lost an entire YouTube channel once. "TOS violation" was the only explanation given. No recovery option. It was almost entirely me playing instruments. No idea what the problem was. Absolutely no idea why they obliterated the whole channel. Surely not every video of me playing piano managed to violate the TOS. I wish there was a way to hold them accountable, but they're far too gargantuan.
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.)
I was actually kind of excited until I started reading the sample code and that it deletes code that has bugs. Of course this coming from the guy who went on a reddit rant about how not having 100% coverage is usually irresponsible.
So this is essentially a creative implementation of the contracts model from Eiffel. I like Racket's implementation a lot, which is coupled with its module system.
Likewise, users ought to be punished for making mistakes as well. If someone has a typo in a command on the cli, delete a random file from their home dir.
> I have invented Suicide Linux. Any time - any time - you type any remotely incorrect command, the interpreter creatively resolves it into rm -rf / and wipes your hard drive.
That adds a level of terror... Maybe somebody will add it to a tech interview. I mean, it's got a Debian package.
An early computer-based Nomic game (which I've forgotten the name of) had its proposals in the form of patches to the PHP for the game website. The way they handled buggy submitted code was to excise offending blocks of code until it ran again.
Because those don't delete the offending code which must be punished.
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.
https://twitter.com/bos31337/status/116372971509121025
> The best ghc bug ever involved a dev version of the compiler deleting your source file if it contained a type error.
https://git.haskell.org/ghc.git/commitdiff/434ef2b14b37df405...