Does not work with CCL

[sdilts]

Looking at the code, CCL is presumably supported, but it fails to compile:

Read error between positions 2119 and 2671 in /home/sdilts/Programs/mahogany/dependencies/cl-freelock/src/atomics.lisp.
> Error: Reader error: No external symbol named "HARD-MEMORY-BARRIER" in package #<Package "CCL"> .
> While executing: CCL::%PARSE-TOKEN, in process listener(1).
> Type :GO to continue, :POP to abort, :R for a list of available restarts.
> If continued: Create and use the internal symbol CCL::HARD-MEMORY-BARRIER
> Type :? for other options.
1 > :POP

When checking if ccl::hard-memory-barrier is just an internal symbol, it doesn't work as a function:

? (ccl::hard-memory-barrier)
> Error: Undefined function CCL::HARD-MEMORY-BARRIER called with arguments () .
> While executing: CCL::TOPLEVEL-EVAL, in process listener(1).
> Type :GO to continue, :POP to abort, :R for a list of available restarts.
> If continued: Retry applying CCL::HARD-MEMORY-BARRIER to NIL.
> Type :? for other options.
1 >

Digging into more of the code, the behavior of the CAS operation that is being used doesn't match what this project's doc string says it does, so the implementation probably won't work anyways.

[ItsMeForLua]

You're right, I do need to update those docstrings and such to reflect what cl-freelock currently is compatible with. Initially when I published, I assumed, (and knew that I was assuming) it was compatible with a few other implementations, but with the plan to test against other implementations eventually, and update the code as needed. I tried to make the code NOT be implementation specific, but, I'm very much used to SBCL, so things get looked over easily.

I think I also originally already planned to update those docstrings and the readme, but, time has left me and I forgot about these things, so thank you for bringing all this to my attention.

I noticed you created a fork:
PR's are welcome for sure, I do plan on getting cl-freelock compatible with other implementations, but within reason. If it would require too much changing of the core code, I may discontinue attempting to adapt to the implementation in question.

Recently, my interests have been in clozure for science related stuff, so we can definitely further this. I don't think it will be too hard to do.

Also in regards to what symbols are and arn't external: I actually have a few pages i had written for the wiki, that I made like 7-8 months ago. I can get that published into the wiki, which hopefully should offer some more convenience. Since there's actually a lot of features available that the readme, and the wiki, both do not cover(yet).

[ItsMeForLua]

I think a lot of the docstrings need to be updated anyway, as some of them were just temporary to begin with. For example 1/4th of the docstring I know for sure are just placeholders, since the original code didnt have any docstrings, and I realized I probably needed some for when I review my code months later(and will inevitably forget why I coded something a particular way), so some of the docstrings probably are slightly wrong at the moment, but they're not necessarily a hazard functionality-wise. Most of them are true in their own ways, but I agree some needs updates.

[ItsMeForLua]

I will be taking steps this months to fix all of these issues. I'm right there will you. If you want to collaborate aswell, I would be open to the help for sure.

To start with, I'm going to investigate the CAS function you questioned. You can expect a follow up sometime this week or early next week.

And I will also briefly scan through the docstrings to see if I can spot anything that needs to be reworded.