Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[ACTOR] actors.lisp and actor.lisp are important examples #27

Open
adlai opened this issue Oct 10, 2024 · 4 comments
Open

[ACTOR] actors.lisp and actor.lisp are important examples #27

adlai opened this issue Oct 10, 2024 · 4 comments
Assignees
Labels
enhance Clicking "enhance" should not violate the laws of physics.

Comments

@adlai
Copy link
Collaborator

adlai commented Oct 10, 2024

Describe the bug
If the underlying CSP library is built according to various presumptions, then the old and different actor.lisp and actors.lisp files will exhibit strikingly different behavior, that could cause hard failures of dependent code.

To Reproduce
Steps to reproduce the behavior:

  1. Copy out old 'actor.lisp'
  2. Copy out old 'actors.lisp'
  3. git bisect --work --your --magic
  4. File new issue and write test cases all teh fuckng time!!

Expected behavior
Minimal test cases resembling obscene user stories; Sophie-Germain prime-sieve orgy.

Screenshots or Error Logs
Text is preferable over screenshots, unless you edit the screenshot to highlight the failure.

System (please complete the following information):

  • Hardware: [all]
  • OS: [any]
  • Compiler [any ... and all]
  • Version [... lambda-adic suicide]

Test Suite
If you have already written tests, please include the output from running the test suite on your target system; if you can't copy output on your target terminal, please provide a verbal summary, including whether it completed and where you subjectively noted most of the resource consumption using your peripheral observations. Note that the test suite might not catch any specific unit failure, and/or might use different fixtures in the cloud than the one you imagined before writing them yourself, and will usually be invoked using (asdf:test-system "chanl").

adlai added a commit to adlai/chanl that referenced this issue Oct 10, 2024
@adlai
Copy link
Collaborator Author

adlai commented Oct 10, 2024

Next, consider whether these belong in fixtures or ASDF-local quicknames

@adlai adlai self-assigned this Oct 10, 2024
@adlai adlai added the enhance Clicking "enhance" should not violate the laws of physics. label Oct 10, 2024
@adlai adlai linked a pull request Oct 10, 2024 that will close this issue
@adlai
Copy link
Collaborator Author

adlai commented Oct 10, 2024

#28 adds the files

#29 should actually do something using them, rather than only publishing like "here is hairball, leach out the Melena pleasanta"

@adlai adlai closed this as completed in #29 Oct 19, 2024
@adlai adlai linked a pull request Nov 20, 2024 that will close this issue
Merged
@adlai
Copy link
Collaborator Author

adlai commented Dec 14, 2024

They could be compared against memento-mori.lisp, the main file from that project; however, the purposes of the two projects seem different. It appears that Kat was specifically working towards Erlang, whereas my inspiration was Ada.

@adlai adlai reopened this Dec 14, 2024
@adlai adlai mentioned this issue Dec 14, 2024
Merged
@adlai adlai closed this as completed in #33 Dec 18, 2024
@adlai adlai removed a link to a pull request Dec 18, 2024
Merged
@adlai
Copy link
Collaborator Author

adlai commented Dec 18, 2024

Incorrectly closed by excessive GitHub automation; this Issue should remain open as a reminder that those two files are ad-hoc, undocumented, and mostly untested.

@adlai adlai reopened this Dec 18, 2024
@adlai adlai removed a link to a pull request Dec 18, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhance Clicking "enhance" should not violate the laws of physics.
Projects
None yet
Development

No branches or pull requests

1 participant