Coding 2024-11-27
So, these last couple days, I was distracted by something I don't think I'll ever explain here (except that I was wrong to doubt myself), but that should be over with now.
Anyway, let's try to get through a bit more of the COCHIS paper before I get ready for bed. As I said before, I got to the Scala section, and I'm having a bit of trouble due to having no Scala experience. I can contrast what I'm seeing so far with how I want to do things in Impliciula, but I'm not sure if there's any point to that; I haven't read far enough to get a sense of what parts of Scala's design they want to highlight. Let's see if I notice any key points in the next few minutes...
"Scala implicits do allow for a wider range of applications than [Haskell] type classes." It then gives an example of this.
Following that, it gives an example of an instance of instability in Scala. I should take the time (which I don't have right now), to carefully study and translate the example, because I don't think I have any reason to expect my current design ideas to just happen to avoid the issue. It could happen, but it would be complete luck on my part.
From a brief look at the example, my intuition is that a naive translation would fail to compile, but it may be possible to "salvage" the instability in some way.
Anyway, it's late; I'd better pack up, etc.
Good night.