Bram Moolenaar wrote: > Currently I decided to keep it relatively simple and only provide three > ways: > > - public: read and write access, using the "public" keyword > - default: read access only, no keyword used > - private: name prefixed with an underscore
It can be fine, but: - it's not symmetric to have a keyword for 'public' members only. Symmetry is nice when possible. - what if the developer changes his mind (changing a member from private to public for example). It requires renaming all occurrences. I'd slightly prefer the 'private' (default) and 'public' keywords and use 'const' or 'final' instead of implicit constness. Later you may decide to add 'protected' if deemed useful enough. I would have preferred 'const' by default and use the explicit 'mutable' or 'mut' to make things changeable as in 'rust', but that would be inconsistent with the regular variables in vim9 unfortunately. Dominique -- -- You received this message from the "vim_dev" maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php --- You received this message because you are subscribed to the Google Groups "vim_dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/vim_dev/CAON-T_gCSh68AK012U6ckTSQK1p5H0zcaQG7D6ci%3D8%3Di%2B0wtSA%40mail.gmail.com.
