Hi -
For those of you working with the master branch of Chapel,
I wanted to point out that I recently enabled the lifetime checker
by default.
If it causes problems for you, you can turn it off with the
chpl compiler flag --no-lifetime-checking
Additionally, if you get confusing errors from the lifetime
checker, I recommend the following strategy for
migrating your code:
* first, convert any constructors to initializers
(expect a deprecation warning for this next week)
* next, compile with --warn-unstable and fix any
issues there. In particular, the relevant part for
lifetime checking is that this flag will ask you to annotate your
class types with unmanaged, borrowed, shared, or owned.
The compiler will interpret an un-decorated class type as a borrow.
I'll be working on creating more documentation about
this for the 1.18 release. For now, the 1.17 release notes discussing
the Delete-Free ongoing effort are the best introduction:
https://www.chapel-lang.org/releaseNotes/1.17/09-ongoing.pdf
Thanks,
-michael
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Chapel-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/chapel-users
