I've been inactive the past few months and no new errors or bugs were reported, I will assume this is a good sign and means the library is ready for 1.0.
I'd still like to implement windows support, but I currently do not have access to a Windows machine irl, so I will put that off for now.
In hindsight, the thread interface is complete jank, but it was the only way I could come up with a workaround of the fact that Julia refuses foreign thread support. This seems to have been fixed in 1.9 so once that version releases in what I assume is 2024, additional devtime may need to be allocated to rework the multithreading interface. I added a warning to the docs to make users aware of this.
I will give this PR a few days before I take the plunge and merge it, if something I made is in 1.0, I want it to be stable, bug-free and optimized. This is very important to me.
I've been inactive the past few months and no new errors or bugs were reported, I will assume this is a good sign and means the library is ready for 1.0.
I'd still like to implement windows support, but I currently do not have access to a Windows machine irl, so I will put that off for now.
In hindsight, the thread interface is complete jank, but it was the only way I could come up with a workaround of the fact that Julia refuses foreign thread support. This seems to have been fixed in 1.9 so once that version releases in what I assume is 2024, additional devtime may need to be allocated to rework the multithreading interface. I added a warning to the docs to make users aware of this.
I will give this PR a few days before I take the plunge and merge it, if something I made is in 1.0, I want it to be stable, bug-free and optimized. This is very important to me.