Replies: 2 comments 1 reply
-
It should be new_init and temp_init if it allocates, init otherwise. I don't think there is any init_new anymore (there might be some use of that still in the docs that isn't updated) But the whole thing is problematic. |
Beta Was this translation helpful? Give feedback.
1 reply
-
Perhaps this would also be a good place to list out what all is needed in the stdlib for 1.0? I can also move this to an issue if that would be better |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
At the moment the way to initialize the data structures in the standard library are not uniform (init_new, new_init, init, etc.). This makes it more difficult to learn the stdlib since you have to memorize all of the different variations for each module. I would like to hear other peoples thoughts on this (and of course @lerno) and ideas as to how it might be unified. The idea I had was something like: new, init, tnew, tinit (in this case new means to allocate the data, and init would initialize it to defaults or values supplied) or other variations of the names (such as create, alloc, etc. for allocation). But let me know what you guys think!
Beta Was this translation helpful? Give feedback.
All reactions