I'd go after the 'cleanup' and 'bug' issues first, or in parallel.
I'm personally most interested in the ones related to buffers, such as
14, 16
Nice to have, would be
15 - replace more builtins with bytecode, but that's very nice to have, and not
strictly necessary
These all seem well scoped, and relatively easy to tackle compared to some
others.
From a 'whew, that makes life easier' perspective, I'd want:
issue 29 - handle all constant declarations
One of my most challenging workarounds relates to int64_t bitfields. I've only
every run across it once.
===============================
- Shaping clay is easier than digging it out of the ground.
________________________________
Date: Mon, 28 Sep 2015 01:32:30 -0400
Subject: What issues does the LuaJIT user community consider the most
important?
From: demetriobenour@xxxxxxxxx
To: luajit@xxxxxxxxxxxxx
There is a list of issues on the LuaJIT GitHub mirror at
https://github.com/LuaJIT/LuaJIT. Which issues does the LuaJIT
community believe are the most important and should be worked on first?
This might provide a rough idea of which issues to start work on. I
feel like doing one issue at a time might be a good way for the
community to start work on the LuaJIT codebase without being
overwhelmed.
