Using either @allow.bareCreate() or @allow.bareCall() creates both create_ and call_ routes

[nullun]

There may be a valid reason for this, but I can't think of it. I would have expected the same behaviour as @allow.create() and @allow.call(), where it only creates the route for whichever one you use.

For example when I specify @allow.bareCall("OptIn") it will add both create_OptIn and call_OptIn. Even though the create_OptIn immediately leads to an err, shouldn't it use NOT_IMPLEMENTED instead?

import { Contract } from '@algorandfoundation/tealscript';

class Demo extends Contract {
    createApplication(): void {
    }

    @allow.bareCall"OptIn")
    my_method(): void {}
}

switch create_NoOp create_OptIn NOT_IMPLEMENTED NOT_IMPLEMENTED NOT_IMPLEMENTED NOT_IMPLEMENTED NOT_IMPLEMENTED call_OptIn

...

create_OptIn:
	err

call_OptIn:
	txn NumAppArgs
	bz abi_route_my_method
	err