The API needs to be stabilized and made more intuitive by making all classes and features behave in a similar way. Right now, for example, one can create a daedalus::script from a buffer or by passing a std::string_view which reads a file. Ignoring for now, that it should take a std::filesystem::path instead, this API should either be available for all classes or be removed in favour of just always passing a buffer.
[x] [implemented in 7e7aff] Another painpoint is the requirement of passing a buffer& to basically all user-facing functions which require one. While it is useful to have this feature within phoenix, users would almost never care about the buffer but they have to keep it around anyways. User-facing functions should always be able to take a buffer or a buffer&& for the user's convenience.
The API needs to be stabilized and made more intuitive by making all classes and features behave in a similar way. Right now, for example, one can create a
daedalus::scriptfrom abufferor by passing astd::string_viewwhich reads a file. Ignoring for now, that it should take astd::filesystem::pathinstead, this API should either be available for all classes or be removed in favour of just always passing abuffer.Another painpoint is the requirement of passing abuffer&to basically all user-facing functions which require one. While it is useful to have this feature within phoenix, users would almost never care about thebufferbut they have to keep it around anyways. User-facing functions should always be able to take abufferor abuffer&&for the user's convenience.