use the construct operator to replace new_init() in the stdlib

[Book-reader]

currently just for the list as I don't have time today to do everything (hashmap, linkedlist, priorityqueue, dstring, etc)

please let me know if this is not wanted or if there are specific places where it is not wanted

[lerno]

This is fine. Do you want to leave it a draft and add more to it?

[Book-reader]

Yes, I will add more tomorrow and see what these failing tests are about

[Book-reader]

ah

+ fn List List.new(usz initial_capacity = 16, Allocator allocator = allocator::heap()) @operator(construct)

Unexpected error in vasplat_function_call.c3 line 4:"This method is already defined for 'List'."

that makes sense why it fails then

[lerno]

I keep being on the fence about this. I don't know if operator(construct) is the right way to do this. I have a weird gut feeling that it's just complicating the language. It's like... static methods are not a thing EXCEPT for this weird special rule.

But then if that special rule is used all of the time, then doing it through "operator(construct)" is weird since it's used all of the time.

It's a whole lot cleaner than opening a new namespace but it's also a very odd corner in the language. I need to think about this.