I sent the following message:
While it's not querying it from the type itself, one thing that you could use is these queries from the Types module:
- https://chapel-lang.org/docs/latest/modules/standard/Types.html#Types.isOwnedClass
- https://chapel-lang.org/docs/latest/modules/standard/Types.html#Types.isSharedClass
- https://chapel-lang.org/docs/latest/modules/standard/Types.html#Types.isUnmanagedClass
- https://chapel-lang.org/docs/latest/modules/standard/Types.html#Types.isBorrowedClass
which I believe will allow you to pass either `from` itself or `fromType` and get a `bool` result. You could then use that to explicitly set the matching memory management in the new declaration (probably by taking advantage of split initialization so that `tmp` can live outside of the `if` statement making these checks
Hope that helps,
Lydia
But it got automatically truncated to:
While it's not querying it from the type itself, one thing that you
could use is these queries from the Types module:
It seems like something about the start of the list caused it to get cut off. I wasn’t seeing any recent reports along these lines (there was one from 2015 that mentioned two - being interpreted as a signature, but that’s not what I wrote and that issue looked resolved)
Did this change recently? Is there a setting we should adjust in our configuration to avoid this behavior?
Thanks,
Lydia