Regarding the parameters of the frb(init) method

[star4277]

Could you please add parameters to the code that has this macro? Because functions like log initialization can be placed within this method. However, when initializing, it is necessary to determine whether it is in debug or release mode to set the level of log printing. But adding an extra method call seems unnecessary and redundant, as all of this belongs to the initialization of frb.

[fzyzcjy]

Good point! may I know what is the ideal way you want to pass the params? it seems that it is called by frb, thus users cannot pass arguments into it currently.

[star4277]

It is preferable to adopt the same approach as the current code generation method, that is, to dynamically generate the parameter list based on the input parameters. For example, the parameters can be encapsulated into an object and passed to the RustLib.init() method. It is possible to pre-agree to pass in the Options type, but the fields related to Options should be mapped to the parameters in the init method. It can be written like this: RustLib.init(options: Options(xxx)). If there are multiple init methods, the parameter naming in Dart can be the name of the init method followed by options, for example, the Rust method is named init_log, then the Dart call is RustLib.init(initLogOptions: xxx).

[fzyzcjy]

Looks reasonable, feel free to PR for this! (I plan to start merging prs after the agent finishes #2990 which I think is soon)