I am looking to get more precision about the statically determined call resolution.
Does this means that the used / exported code of a module will be redeployed along the importer bytecode ?
These quotes are from the Move whitepaper :
No dynamic dispatch. The target of each call site can be statically determined. This makes it easy for verification tools to reason precisely about the effects of a procedure call without performing a complex call graph construction analysis.
This ensures that all procedure calls in Move are statically determined — there are no function pointers or virtual calls.
The execution of bytecode proceeds by executing operations in sequence unless there is a branch operation that causes a jump to a statically determined offset in the current procedure.