say you are programming your new favourite garbage collected unityped language.

[dysfun@social.treehouse.systems]

@typeswitch i will probably save this for the less unityped version, where i want to do stuff like simd that doesn't fucking suck

[deech@mastodon.social]

@dysfun jamming away on Tcl at the moment but that probably doesn't qualify as "new" or "favorite" but it's less hassle and has some other nice ecosystem properties

[dysfun@social.treehouse.systems]

@deech yes it's so new i haven't written it yet. what should it look like?

[deech@mastodon.social]

@dysfun probably like Shen without the typechecker

[dysfun@social.treehouse.systems]

@deech huh? literally everything i know about shen is about its types

[deech@mastodon.social]

@dysfun unless something has changed types are optional and type checking has to be explicitly enabled

[dysfun@social.treehouse.systems]

@deech it's entirely possible i missed the point, but i thought the point was the types?

[zardoz03@mastodon.online]

@deech
i highly doubt theres a lisp thats unityped without being a turing tarpit of conses. theres probably a hard minimum of types needed that like picolisp uses, but its not 1
@dysfun

[deech@mastodon.social]

@dysfun when i did my talks on Shen I hyped the types but even without its still a nice Lisp with pattern matching and TCO.

[dysfun@social.treehouse.systems]

@deech yeah i feel like there will be pattern matching at least.

but i'm still not convinced the market for a lisp is very large.

[lunadragofelis@void.lgbt]

@dysfun If the one type can be "object", the one type will be object.

#Kittyscript (the language I'm actually developing) is pretty close to it, every value has a method handler associated with it. That's a function which gets the object as the first argument, the method name as the second and followed by the arguments to the specific method. An object can also be used like a function, if it has a __call method.

Some objects (that are implemented as Kittyscript records or implement the KsObject interface on the Java/Kotlin level) have individual method handlers, while other objects (including Kotlin and Java objects) get handled by a "fallback" method handler that also dispatches on the type of the object.