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
Right now, knowledge and logic of how to access and manipulate lists is spread across LoxList, Interpreter, and NativeFunction. Moreover, there is currently a loophole of sorts which allows instantiation of a List but that doesn't have any of the features of a LoxList, and this is also potentially confusing to users. There ought to be a way to centralize all the business logic for handling of lists, and to close the loophole.
The text was updated successfully, but these errors were encountered:
Right now, knowledge and logic of how to access and manipulate lists is spread across
LoxList
,Interpreter
, andNativeFunction
. Moreover, there is currently a loophole of sorts which allows instantiation of aList
but that doesn't have any of the features of aLoxList
, and this is also potentially confusing to users. There ought to be a way to centralize all the business logic for handling of lists, and to close the loophole.The text was updated successfully, but these errors were encountered: