@wallhackio fuck you
@wallhackio hey clod boy
i know what you want
but please protect your wrists so you can keep doing your job
@Satsuma @wallhackio @amy listen to your weird gay cousin
@Satsuma @wallhackio i do not remember this story i’m just astounded at how obviously bad that idea is
@wallhackio bruh
@amy *absol voice* nyaaaaaaaa
re: pendantic terminology question
@wallhackio anyway here is something i think about that to me complicates the nomenclature at play here
now, this is not the entirety of use cases fur exception handling, but a very compelling use case fur exceptions is to handle impawsible situations about as gracefully as pawsible—even if by just crashing. the way erlang does, i guess. put a pin in that
consider you are using a strongly typed language with algebraic data structures, in which it is natural to define a data type that represents an abstract syntax trees. assuming there are no bugs in the AST definition, any construction you can make in the AST that type checks is a syntactically valid statement in the language you are writing an AST fur
so, imagine trying to compile source code whose contents entirely consist of constructing an AST in this language. if this fails to compile, you are trying to repurresent a local impawsibility, and the compiler will stop execution
is it a valid way to think about compilation in general in these same terms? is a compiler error better thought of as an expected result, or as an error state resulting from the compiler being forced into a logically impawsible state by the context in which it is oppurrating? which is to say, is it valid to conceive of compile time errors as the compiler assuming it is oppurrating in a logically consistent world, and exploding in response to a discovered inconsistency?
re: pendantic terminology question
@chr this was a great post imo
@monorail is this a joke of some kind
re: pendantic terminology question
@wallhackio huh
it’s pronounced “ashling”. canonically a black housecat or any of the grass cat pokémon, but currently experiencing daily TFs. Commewnist. she/it
GlitchCat syscatmin and meowstodev; @ me about techincal problems with the instance, or fur feature requests. i got a job due to some extent to my work on this instance
i have very strong opinions about the sonic furanchise. pokémon has me in a chokehold when it comes to merchandise
available via email with the same username and domain. DM/email for other purrotocols
workplace policy is to clarify that all of my opinions expressed here are my own, and not those of my employer
“all this shit is still incomprehensible but im glad u accomplished something” ―@wallhackio
“i feel mildly relieved that the obscure and esoteric code that i use to build the site will always be definitely outclassed by the obscure and esoteric code that you use to serve it” ―@Lady