Patrick Hammer

good find, and feel free to fix it yourself, it would be good for v3.0.1!

solved by https://github.com/opennars/opennars/commit/ef50447ab4b207b7b69b28fc99f5e17e094c668b

This issue should not be closed as the issue is still existing!

"One way which is compatible with the preallocation philosophy of memory managment is to add a custom memory allocator + manager under AIKR for entry's which are utilized." I agree...

The UI only works on Windows, so it's not worth it, you would also loose the configuration ability for your monster machine .NET currently offers. Maintainence shouldn't be an issue...

Best practice would not be to move to new version for new versions sake. Instead it should be configured to compile with >=2.2 so that it will build with 2.2...

I see, makes sense. Should also work with a >=2.2 config though hm. To avoid corruption of config file you can also update .gitignore to exclude the dotnetcore files, this...

Cool, I will create a PR accordingly! And I agree, it will be better if it will be a separate print function `pprint` or if you prefer something more verbose...

TODO make sure revision of prototypes works in case an instance is mentioned again (as can happen if for instance the preprocessing also tracks instances over time)

Nalifier is merged into master ( https://github.com/opennars/OpenNARS-for-Applications/pull/226 ), and a working example with real-time camera-feed is provided and showcases on Youtube: https://www.youtube.com/watch?v=ny_AVZLE2X0 New perception systems for ONA will be based...