Should the SurrealQL type conversion functions in the type module be moved into a separate submodule?

[matthewjnield]

The SurrealQL functions module type (https://surrealdb.com/docs/surrealdb/surrealql/functions/database/type) currently contains three broad groups of functions:

• Functions that check whether an input value is of a certain type, such as type::is::string. All of these functions are contained in the submodule type::is, whose name effectively signals the intent that the function is checking for the given type.

• Functions that convert/coerce an input value to a certain type, such as type::string. All of these functions are currently contained directly in the module type.

• The type::field and type::fields functions.

I think that moving the second category of functions, which convert/coerce their input value to a certain type, into their own submodule would have the following benefits:

• Clearer intent of SurrealQL code using the conversion functions, just like the functions in the type::is submodule.
• Clearer distinction of the two large groups of functions in the type module and their purposes, slightly improving the experience of those learning SurrealQL.
• An overall slightly better organized function API for SurrealQL.

Ideas for clear names for this submodule that come to mind include type::as and type::convert.