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.

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

Jump to bottom

nimrod serve crashes on wrong usage #344

Closed
reactormonk opened this issue Feb 22, 2013 · 1 comment
Closed

nimrod serve crashes on wrong usage #344

reactormonk opened this issue Feb 22, 2013 · 1 comment
Assignees
@zah
Labels
Tools

Comments

@reactormonk
Copy link
Contributor 

nimrod serve --server.type:stdin foo.nim
idetools --track foo.nim,1,1 --suggest
command line(1, 1) Error: argument for command line option expected: 'track'
command line(1, 1) Error: 'FILE,LINE,COLUMN' expected
command line(1, 1) Error: `ów is not a valid number
SIGSEGV: Illegal storage access. (Attempt to read from nil?)
@ghost ghost assigned zah Feb 22, 2013
@Araq
Copy link
Member

Araq commented Mar 12, 2015

Nimsuggest is the future.

@Araq Araq closed this as completed Mar 12, 2015
@eulores eulores mentioned this issue Nov 12, 2021
Closed
Clyybber pushed a commit to Clyybber/Nim that referenced this issue Jul 12, 2022
@bors @saem
Merge nim-lang#344
220a06a 
344: sem: clean-up TContext docs, readers, and writers r=saem a=saem

## Summary
* documented each field for TContext, purpose, writers, and consumers
* docs to understand the compiler internals and what needs fixing
* remove dead code, fix bugs/issues in writers/consumer of the data

## Details
* removed dead fields: evalContext, unknownIdents, symMapping, etc
* documented refactor strategy to allow this to be a longer lived refactor



Co-authored-by: Saem Ghani <saemghani+github@gmail.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@zah zah

Labels
Tools
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@reactormonk @zah @Araq