fsprojects/FsLexYacc

Issues

• "unrecognized input" after upgrade

  #208 opened a month ago by danabr
  1

• Publish the ASTs and parsers for the ASTs for the FsLex and FsYacc tools to enable more robust editor tooling

  #143 opened 2 months ago by baronfel
  13

• Online grammar editor/tester

  #195 opened 3 months ago by mingodad
  0

• removing the need for explicit numbering of enums in F#, possible fixing problem with struct decorated DU's without fields.

  #173 opened 7 months ago by kam1986
  0

• LexBuffer<char>.LexemeSpan

  #172 opened a year ago by bent-rasmussen
  0

• error recovery is poorly documented

  #67 opened 8 years ago by chrismacklin
  6

• Invite you to try FslexFsyacc

  #156 opened 2 years ago by xp44mm
  7

• How to get a position of a token from ParseErrorContext

  #162 opened 2 years ago by artempyanykh
  1

• %% Trailer seems not supported

  #164 opened 2 years ago by fxf06
  0

• API Documentation issues

  #163 opened 2 years ago by fxf06
  0

• Question: Can we get FSLex to embed a comment with the date-time that the outputs were generated?

  #155 opened 3 years ago by Korporal
  1

• Activating case insensitive option crash the lexer generator

  #141 opened 2 years ago by lkluc
  12

• How to turn on runtime debug output

  #159 opened 2 years ago by artempyanykh
  0

• Equals for NfaNodeIdSet always returns false

  #41 opened 3 years ago by bronti
  3

• Invite you to try a new series of Lex/Yacc tools

  #151 opened 3 years ago by xp44mm
  9

• Reductions table being recreated on each parser invocation

  #139 opened 3 years ago by dsyme
  0

• a syntax highlighter for fslex, fsyacc, F#

  #152 opened 3 years ago by xp44mm
  0

• Building a project which uses FsLex/FsYacc fails when building with Visual Studio 2019

  #142 opened 3 years ago by glenbraun
  2

• Can't find the FSharp.Text.Lexing and FSharp.Text.Parsing lib?

  #148 opened 3 years ago by kam1986
  1

• Not an issue more like an optimization

  #147 opened 3 years ago by kam1986
  2

• Variables in supplied ".target" file seems undefined leading to compilation error

  #140 opened 3 years ago by lkluc
  6

• Emit tables for better diagnostics

  #138 opened 3 years ago by dsyme
  0

• FsLexYacc broken under .net 5.0 runtime only

  #134 opened 4 years ago by pchalamet
  7

• Using F# keywords for non terminal names does not compile

  #132 opened 4 years ago by thautwarm
  4

• target file Error

  #99 opened 4 years ago by kam1986
  1

• Case insensitive option

  #102 opened 4 years ago by lkluc
  0

• Weird context sensitive error in FStar's parse

  #68 opened 4 years ago by kyoDralliam
  2

• How can I count/enumerate all syntax errors that occur while parsing?

  #72 opened 4 years ago by siddharth-krishna
  4

• Incorrect self-referencing line directives in generated files

  #73 opened 7 years ago by miegir
  0

• Suggestion: place code block from .fsy after token declaration in generated .fs

  #74 opened 7 years ago by miegir
  0

• Executable bit not set for tools in nuget package

  #64 opened 4 years ago by dsyme
  2

• Suggestion for MSBuild docs

  #55 opened 4 years ago by daz10000
  3

• Fix broken CI tests

  #84 opened 4 years ago by kkm000
  1

• Support netstandard

  #78 opened 4 years ago by mrgleba
  16

• FsLexYacc.Runtime.dll does not represent a strongly named assembly

  #81 opened 6 years ago by llly
  4

• FSharp.Core Dependency

  #96 opened 5 years ago by fangyi-zhou
  12

• A local version of the site is mistakenly published

  #105 opened 5 years ago by teo-tsirpanis
  1

• Links in documentation website are broken

  #108 opened 5 years ago by NatElkins
  1

• Switch to SDK-style projects!

  #87 opened 5 years ago by kkm000
  10

• Generation of standalone lexer/parser source file

  #79 opened 6 years ago by nshibano
  3

• Issue with running fsyacc with -v flag

  #66 opened 7 years ago by BartekSTRX
  3

• Doc generation not working

  #63 opened 8 years ago by dsyme
  5

• parseState.ResultRange reports incorrect position info

  #65 opened 8 years ago by nshibano
  0

• add FSharp.Core as nuget package reference

  #46 opened 8 years ago by enricosada
  2

• AssocTable ctor is expensive

  #54 opened 8 years ago by tokreutz
  0

• Support for line start in regular expression

  #57 opened 8 years ago by rixatron
  1

• Issue with reduce/reduce conflicts

  #40 opened 9 years ago by TorbenMogensen
  0

• %nonassoc not handled correctly

  #39 opened 9 years ago by TorbenMogensen
  14

• Windows Appveyor build fails on alternate PRs

  #53 opened 8 years ago by jackfoxy
  5

• LexAndYaccMiniProject test project build fails

  #42 opened 9 years ago by bikallem
  0