Specifically, the two views of typing.
But my fault for linking to a mediocre blog post.
1,757 karma · joined January 20, 2015
Specifically, the two views of typing.
But my fault for linking to a mediocre blog post.
What it comes down to is a reconciliation between these two views: https://ncatlab.org/nlab/show/intrinsic+and+extrinsic+views+...
I think the "reliability" you mentioned is "type safety". And I think the dynamicism I sometimes miss in a language with static types is, in a bizarre way, the lack of runtime type errors. If you load a configuration file, necessarily at runtime, but the configuration file has the wrong format, an error should occur. What kind of error? In essence, a type error...
Reusing the type checking machinery at runtime is a benefit to some. At the same time, the possibility of type errors (type unsafety) is a threat to the reliability of programs.
I have trouble wrapping my head around it, but I ultimately want the bikeshed with both windows.
The typing available in CL, is it like Python type hints in that they don't affect the meaning of a program whatsoever?
There is often a discussion drawn between a computer algebra system and an interactive theorem prover, but to be honest, I don't fully understand what the distinction means.
You might like this talk! "Liberating the Smalltalk lurking in C and Unix - Stephen Kell" https://news.ycombinator.com/item?id=33130701
What due diligence are you talking about? Personal research? (Genuine curiosity)
But I'm even less sure what conceptual reasoning is.
- parametric polymorphism (generics, templates, ...)
- ad hoc polymorphism (type classes are the nicest example)
- https://en.wikipedia.org/wiki/Row_polymorphism I think this one is the most relevant for the record discussion.
What is the gap between e.g. `apt` and Homebrew?
From the same discourse thread.
Interoperability across languages with FFI is an option, but it comes at a cost. Even if the two languages have polymorphism, e.g. with parametric types, the interfaces are almost always monomorphic.
programming can also be about producing generic solutions that commit to some minimal set of assumptions so that solutions work across a variety of contexts, e.g. regardless of whether your data is floats or ints.
sometimes good engineering is about finding decisions you can avoid making or thinking about. Sometimes you have to decide how to add the numbers bit by bit, but for that particular example, it's even better to not care about how the numbers are added up (which is a detail of the CPU or a bignum library or whatever).
But int + int is isomorphic to bool*int.
The unions you're talking about necessarily require a notion of subtyping, I believe.
I thought it was Raymond Chen's blog but I haven't been able to find it. I thought someone here might recall and have a pointer.
I threw up some content up here: https://intellec7.notion.site/Drinking-SICP-hatorade-and-why... , along with an unrelated criticism of SICP.
I'd like to better understand what the limitations are of "everything is just a function".
What are the solutions? You would need multiple merge queues.
Sara Acour has some answers, e.g. https://scholar.google.com/citations?view_op=view_citation&h...