Feedback on "createRegExp" TODO comment

Lines 153 to 157 in 75f1d47

    
           // TODO: do we need this factory function, or can we invoke 
        
           // the ctr via the loader? 
        
           export function createRegExp(regex: string, flags: string): RegExp { 
        
             return new RegExp(regex, flags); 
        
           }

The RegExp constructor is exported as exports["RegExp#constructor"] with a signature of (this_: RegExp, regex: string, flags: string) => RegExp (all pointers, the this_ argument is typically 0 to indicate that the ctor should allocate on its own, i.e. not a super() call). During demangling, the loader creates a function exports.RegExp one can use with and without new representing it, and one can invoke new exports.RegExp(regexPtr, flagsPtr) (without this_) effectively corresponding to exports.createRegExp(regexPtr, flagsPtr), but returning a wrapper class instead of just a pointer.

There may be value in exposing createRegExp, though, for where the loader is not used, i.e. when running the binary in a C or Rust host. The AS compiler typically does this to also provide an easy to use C-like interface that works everywhere.

	// TODO: do we need this factory function, or can we invoke
	// the ctr via the loader?
	export function createRegExp(regex: string, flags: string): RegExp {
	return new RegExp(regex, flags);
	}