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
The separate ".eto()" and ".etr()" methods are nice, but for some applications it would be easier to just pass the surface type directly to a method (instead of having a conditional in the application that picks which method to call).
Since it seems confusing to have "etsz()" and "_etsz()" methods, I think it might be easiest to rename the current "_etsz()" method to something like "_eq1()".
The text was updated successfully, but these errors were encountered:
The separate ".eto()" and ".etr()" methods are nice, but for some applications it would be easier to just pass the surface type directly to a method (instead of having a conditional in the application that picks which method to call).
Since it seems confusing to have "etsz()" and "_etsz()" methods, I think it might be easiest to rename the current "_etsz()" method to something like "_eq1()".
The text was updated successfully, but these errors were encountered: