expose assertion annotations through AssertionError instances

[CeylonMigrationBot]

[@Zambonifofex] The title is pretty self explanatory. It means that if you have an assertion with annotations, the AssertionError thrown will contain the instances of the annotations' classes.

try
{
    "foo"
    bar baz qux assert(exists obj);
}
catch(AssertionError error)
{
    print(error.annotations);
}

The other day I was just thinking about how useless annotations in assertions are. It feels weird to allow such thing only so you can have the doc annotation there. I thought then: to solve the problem "they don't do anything", instead of disallowing them, why not make them actually do stuff?

[Migrated from ceylon/ceylon-spec#1463]

[CeylonMigrationBot]

[@gavinking] That's an interesting idea.

[ghost]

Seems to me that since 1.3.2, an assertion’s documentation can’t be seen as an annotation anymore (since now it can accept interpolation).

So I think this should be closed. What do you think, @gavinking?

[gavinking]

@Zambonifofex This was actually not a bad idea at all. I like it! But yeah, I guess it's out of the question now.