You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Up to now functions could be stored as node values in frame
(as for interpreter defined functions) or function values,
directly callable by the Go runtime. We now always store functions
in the later form, making the processing of functions, anonymous
closures and methods simpler and more robust. All functions, once
compiled are always directly callable, with no further wrapping
necessary.
Fixestraefik#1459.
Up to now functions could be stored as node values in frame
(as for interpreter defined functions) or function values,
directly callable by the Go runtime. We now always store functions
in the later form, making the processing of functions, anonymous
closures and methods simpler and more robust. All functions, once
compiled are always directly callable, with no further wrapping
necessary.
Fixestraefik#1459.
Up to now functions could be stored as node values in frame (as for interpreter defined functions) or function values, directly callable by the Go runtime. We now always store functions in the later form, making the processing of functions, anonymous closures and methods simpler and more robust. All functions, once compiled are always directly callable, with no further wrapping necessary.
Fixes#1459.
The following program
sample.go
triggers an unexpected resultExpected result
Got
Yaegi Version
0218249
Additional Notes
First noticed this when trying to append a list of custom function types, but also breaks with func literals.
The text was updated successfully, but these errors were encountered: