Does Adept have the concept of const-correctness like C/C++?

[ghost]

I have a quick read of the document, and it seems the const keyword is not even supported. Please correct me if I'm wrong.

[IsaacShelton]

Yes correct, const variables are the closest thing, but types themselves cannot be const.

This was mainly done to prevent the const combinatorics you get in C++. Const types can work, but I think the language has to heavily buy into them from the start (which Adept 2.0 didn't), and also opt-in mutability would be better to assume const by default.

These will be things to consider for Adept 3.0

TL;DR Types themselves can't be const

[ghost]

I'm trying to translate a C header, and it uses const very heavily. I didn't ask for this feature, though. I only want to know how to correctly translate them, and it seems I could just ignore const in my translation.

[IsaacShelton]

@iahung2 Yes, you can just ignore const, as it doesn't have an actual impact on the code

So int shape_get_sides(const Shape *shape); would be translated to foreign shape_get_sides(shape *Shape) int