Request Help on Fault Tolerance with `read.ss`
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 15/100
- Issue type
- Feature
- Clarity
- Needs clarification
- Activity status
- Stale
- Domain
- backend
Research direction
The issue discusses making s/read.ss fault tolerant and asks for parser design guidance. Start by reading s/read.ss and the described rd-error handling; the issue does not name tests or a specific change. Done would require a defined fault-tolerance approach and criteria for handling malformed input without unexpected reader errors.
Written by the indexing model from the issue text.
Description
Well, I'm fixing Scheme-langserver's crashes nowadays and one of the most important approach is to catch 79 lines of rd-error like
(xcall rd-error #f #t "invalid string character \\~c~c~c" c c1 c2)
In editor's general scenarios, properly processing them means fault tolerance technique to delete characters and preserve meaningful fragments in source codes as long as possible. For example, R7RS string "\123" may cause error and throw condition, and condition-irritants consists "invalid string character ...", #\\ character's position and other information. My current approach is to replace #\\ character with blank, so that other items in this altered source code will keep their position with origin and won't cause code editing inconsistent with language server indexing.
Here, my current approach is to step-by-step digest s/read.ss and patch downgrade rules to properly handle such rd-errors. And I want following helps:
- Is there any mature compatible solution with Chez's
s/read.ss? If there is, I can be free from dozen of hard workings. - Or, is there any theory publishes on "fault tolerant in lisp parser"? If there is, I can confirm that correctness my patch rules perform.
- Any other advises?
- Addition: apparently,
s/read.ssis not initially designed for fault tolerance, could I say that my patches can't reach the ultimate end, in which positionreadprocedure won't throw unknown errors.
- Dominant language
- Scheme
- Stars
- 7.4k
- Forks
- 1k
- Avg merge
- 1d 20h
- Merged PRs (30d)
- 19
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from cisco/ChezScheme
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
cisco/ChezScheme#1110 ·
Maintainers usually reply within 1 day
-
Difficulty 4/5 3-5 days Newbie friendliness 30/100
cisco/ChezScheme#1111 ·
Maintainers usually reply within 1 day
-
Difficulty 5/5 Over a week Newbie friendliness 12/100
cisco/ChezScheme#1101 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
cisco/ChezScheme#1078 · 1 comment ·
Maintainers usually reply within 1 day
-
RFC: solution to clangd not finding "scheme.h"Possibly taken @reginaldalfret claimed this 20 days ago. Open
Difficulty 4/5 3-5 days Newbie friendliness 48/100
cisco/ChezScheme#1073 · 1 comment ·
Maintainers usually reply within 1 day
All issues in cisco/ChezScheme
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
Kludex/python-multipart#375 ·
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
Termix-SSH/Plugin-Hosts-Config#14 · 1 comment ·
Maintainers usually reply within 4 days
-
bug good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
quantum-php/framework#692 ·
Maintainers usually reply within 1 day
-
area:web kind:bug priority:p2 ready
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
Maintainers usually reply within 1 day
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
Maintainers usually reply within 11 days