Isaac Shelton

Currently, not really, but this is definitely a feature that should exist. This is a glaringly obvious gap in the language, so I'll put high priority on developing this feature...

Resolved! Proper classes and virtual dispatch added in [Adept 2.7](https://github.com/AdeptLanguage/Adept/releases/tag/v2.7) ``` import basics class Shape () { constructor {} virtual func draw {} } class Rectangle extends Shape (w, h...

As of Adept v2.6, weak ownership references do not know whether underlying data is still alive. It's up to the programmer to only use weak references if they are valid....

Yeah, the compiler doesn't guaranteed safety for them. Using previously donated strings should probably be a runtime error like you describe. You can however check the ownership status of a...

Yes `donate()` should probably raise a runtime error if the subject string doesn't have ownership. With `commit()`, sometimes you only want to transfer ownership if it's possessed. So instead of...

1. Yes. There is a full language spec PDF under releases which may interest you, although it is pretty high level at explaining stuff. More documentation will be coming soon...

`in`, `out`, and `inout` are annotations to help the programmer understand the data flow of a function. ``` func getMessage(out message **ubyte) successful { /* ... */ } ``` is...

1. `2.1`, `2.2`, and `2.3` are different versions of the standard library (that correspond to the respective Adept versions that they were made for. It's best to use the latest...

Yeah it is similar to `gcc -std=`. All it does is tell the compiler that it expects features from Adept 2.2 to be available. You can ignore it.

@t0md3an I hadn't thought of doing that... That's a good idea. My one concern is that the version of the stdlib that the program intends on using might not be...