Dave Abrahams
Dave Abrahams
@stt Nice! have you submitted a PR with that?
@lucteo let's try to move open PRs forward and get them merged, or close them please.
It works when it works. I suppose if the step just modifies the filesystem, that's most of the time. However, I still can't describe my CI process in one way...
That sounds promising indeed!
Another possibility would be to provide a `shell:` setting that causes a `run` command to run in the devcontainer. That would cover most of my problems.
According to his [original post](https://val-qs97696.slack.com/archives/C03676BJBUZ/p1715550356911059) this came from direct experience attempting to talk about it with people. It's not about what the parser can handle; it's about what humans digest...
I don't think these will be the only opaque (or nominal, for that matter) types if we have `newtype`, nor, probably, if we have `enum`. I don't think `impl` works...
“Opaqueness” simply means some details of the type can be private (and are by default, but that's not very important here). Such details include the type's list of stored properties....
eIndeed, see [my earlier remark](https://github.com/hylo-lang/hylo/issues/1477#issuecomment-2123162327). Not presuming to speak for @kyouko-taiga but my understanding is that she is unimpressed by these arguments but willing to change the name if a...
> `struct` should win. That's welcome news. I think there are other good reasons for this choice, and not to spend `type` on this, but I've made all of them...