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
In version 0.5.0, it appears that moo deprecated method has and it now always returns true. Since the Nearley parser uses method has, the code it generates now always succeeds producing incorrect results. While I do understand that the moo project has a right to deprecate their interfaces, I'm wondering whether the impact to the Nearley parser was taken into consideration? Also, what was the reason for deprecation of the method has, for example, did it not work correctly in the update from v0.4.3 to v0.5.0 hence it's deprecation because moo internals changed and it could no longer be supported? Would the v0.4.3 code for the method has still work, if I hacked it back into the source for the latest version of moo? Thx.
The text was updated successfully, but these errors were encountered:
In version 0.5.0, it appears that moo deprecated method has and it now always returns true. Since the Nearley parser uses method has, the code it generates now always succeeds producing incorrect results. While I do understand that the moo project has a right to deprecate their interfaces, I'm wondering whether the impact to the Nearley parser was taken into consideration? Also, what was the reason for deprecation of the method has, for example, did it not work correctly in the update from v0.4.3 to v0.5.0 hence it's deprecation because moo internals changed and it could no longer be supported? Would the v0.4.3 code for the method has still work, if I hacked it back into the source for the latest version of moo? Thx.
The text was updated successfully, but these errors were encountered: