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
Where the recovery expressions are because of the following error messages:
error: invalid operands to binary expression ('size_t' (aka 'unsigned long') and 'Experiment')
error: no matching constructor for initialization of 'Experiment'
The text was updated successfully, but these errors were encountered:
One of the root causes for the second error is that some user-defined classes may not have a default constructor, and in reverse mode, we create some global variables at the start of the function and are assigned values later, for ex., in the above example, t1 is declared in the start and assigned later to E.
I can't think of any way other than to explicitly tell the user to make sure that custom classes have a default constructor.
Minimal example:
The starting of the generated function of
f_grad_0
contains the following snippet:Where the recovery expressions are because of the following error messages:
The text was updated successfully, but these errors were encountered: