Editing Online Developer Meeting (2024-01-23)
Jump to navigation
Jump to search
The edit can be undone. Please check the comparison below to verify that this is what you want to do, and then publish the changes below to finish undoing the edit.
Latest revision | Your text | ||
Line 9: | Line 9: | ||
** '''Discussion about "nargout <=" vs "nargout ==", making a policy of "nargout <=" and "nargout >=" going forward, no equality.''' | ** '''Discussion about "nargout <=" vs "nargout ==", making a policy of "nargout <=" and "nargout >=" going forward, no equality.''' | ||
** '''Discussion about iterators and range-based loops and auto types.''' | ** '''Discussion about iterators and range-based loops and auto types.''' | ||
* Blocking tasks before moving any classdef-based class (e.g., string, table, datetime, ...) into Octave core? | * Blocking tasks before moving any classdef-based class (e.g., string, table, datetime, ...) into Octave core? | ||
** '''There is already classdef in Octave core, like inputParser. The difference is that typically there is only one object of inputParser, but Octave core doesn't currently have arrays of classdefs, which would be necessary for arrays of strings etc. See [https://savannah.gnu.org/bugs/?65179] for example''' | ** '''There is already classdef in Octave core, like inputParser. The difference is that typically there is only one object of inputParser, but Octave core doesn't currently have arrays of classdefs, which would be necessary for arrays of strings etc. See [https://savannah.gnu.org/bugs/?65179] for example''' |