-
Notifications
You must be signed in to change notification settings - Fork 481
Lacking string -> enumerable<string> #41
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
Comments
@davhdavh, I think that terminal call some platform specific API. This will be a cool enhancement and will be scheduled when it reaches stable status. I've already reasoned of it in past, but nobody asked for it. I think too it could be useful! :) Thanks for posting it! (Please be patient until -> stable). 👍 |
Command Line actually include some source file with Paket. These files are not included in the git repo, but you can get it from a terminal: $ cd CommandLine
$ .\packages\Paket.1.19.7\tools install As said in first post, I can't accept PR of type enhancement until beta becomes stable (and fit in this state without serious issues for a some time, to be fair). I've not done a detailed code review, but in general keep in mind that 2.0.x was born for rewrite the kernel in functional style. Your pre-tokenizer could be in static class with a static member: Could be public or we can add a But please wait for stable... Anyway thanks for your ideas and work. :) |
That's fine, you have the code for the actual parsing when you need it. On Tue, Sep 1, 2015 at 10:05 AM, Giacomo Stelluti Scala <
Dennis |
Does the 2.0.x-stable label mean that this issue has to be solved for the 2.0 branch to become stable, or that the issue wont be worked on until 2.0 is stable? |
Sounds like this is intended to be worked on after stable is reached. |
Friday Aug 28, 2015 at 10:13 GMT
Originally opened as gsscoder/commandline#232
There seems to be no support for NOT depending on the OS parsing of the arguments string.
In my case, I am parsing a command line from a chat program.
The text was updated successfully, but these errors were encountered: