Dave Abrahams
Dave Abrahams
I understand what you're getting at, but would prefer not to use the term “forward,” which implies some kind of order-dependence. Maybe just "declare" or "declaration_only?" I think this ought...
> ``` > // In Library/Hylo/Core/Assert.hylo > @declare_only > public fun fatal_error(...) -> Never > > // In MyDriver.hylo > @definition("Hylo.fatal_error") > public fun fatal_error(...) -> Never { ... }...
Working on this; see #787
Keep in mind that not all tests run on Windows because of #1289 Is that perhaps why you're not seeing the failures?
AFAICT `f` does need the `inout` effect because pointer dereference is just a regular projection. If you wrote: ```swift &(p.copy().unsafe[]) = 19 ``` It would not.
> only way to achieve that is to use ordered data structures everywhere. We can still use hashed data structures but we might need to write them ourselves (or just...
It bothers me too. It's a known SPM bug and I don't know what to do about it (the files are in fact handled, by the plugin). It will happen...
> I use a command-line script anyway on my system Then (1) would be a perfectly good solution for you. It's easy enough to filter them out.
one challenge I've had with this is that I can't figure out how to run a test under the debugger in the release build. I'm getting link errors. Anyone able...
I can run the debugger and get a stack trace, but there is no information about variables. Are there any facilities for dumping information about the state of things?