Skip to content

Issues: s-expressionists/Eclector

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.

Sign up for GitHub

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

11 Open 64 Closed
11 Open 64 Closed
Author
Filter by author
Loading
Label
Filter by label
Loading
Use alt + click/return to exclude labels
or ⇧ + click/return for logical OR
Projects
Filter by project
Loading
Milestones
Filter by milestone
Loading
Assignee
Filter by who’s assigned
Sort
Sort by
Newest Oldest Most commented Least commented Recently updated Least recently updated Best match
Most reactions
👍 👎 😄 🎉 😕 ❤️ 🚀 👀

Issues list

Query: is the source code for the demonstrations from your presentation available? question Further information is requested
#76 opened Jan 20, 2023 by rpgoldman
@scymtym
5
read-from-string's source don't take into account :start bug Something isn't working unclear-in-spec Issues related to unclear parts of the spec
#75 opened Mar 31, 2022 by fstamour
2
Single quote bug in parse-result documentation Something should be documented
#69 opened May 22, 2020 by ruricolist
5
Handle reading of floating point numbers better enhancement New feature or request
#68 opened May 15, 2020 by scymtym
13
QUASIQUOTE can't handle circular lists
#60 opened Dec 9, 2019 by Bike
1
Extension: Decimal syntax for rationals enhancement New feature or request wishlist Low priority
#54 opened Jun 4, 2019 by scymtym
Document how to use Eclector as the reader of an CL implementation documentation Something should be documented
#53 opened May 31, 2019 by scymtym
@scymtym
ppppp:[:]nnnnn should probably result in an error enhancement New feature or request
#44 opened Mar 27, 2019 by scymtym
Test readtable implementation enhancement New feature or request test A test should be written or improved
#32 opened Aug 11, 2018 by scymtym
@scymtym
Ensure every CST element has a SOURCE, suggest how to capture whitespace and comments question Further information is requested
#28 opened May 24, 2018 by eschulte
@scymtym
6
Add a test to check that *READ-SUPPRESS* causes READ to return NIL enhancement New feature or request test A test should be written or improved
#3 opened Feb 28, 2018 by scymtym
@scymtym
ProTip! Exclude everything labeled bug with -label:bug.