Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • why3 why3
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Graph
    • Compare
  • Issues 166
    • Issues 166
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 26
    • Merge requests 26
  • Deployments
    • Deployments
    • Releases
  • Packages and registries
    • Packages and registries
    • Container Registry
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
Collapse sidebar
  • Why3Why3
  • why3why3
  • Issues
  • #132
Closed
Open
Issue created Jun 13, 2018 by Guillaume Melquiond@melquionOwner

Make why3doc syntax less error-prone

Why3doc offers [...] for embedding code inside comments, but people tend to misuse it. I have already fixed a lot of instances of this issue. I even tried to improve the lexer in 1827453a to workaround the issue. But people keep misusing it. As a consequence, several examples cannot be uploaded to the gallery due to how broken they look.

So, I now propose a much drastic change: forsaking the [...] syntax in why3doc and switching to a Markdown-like syntax: `...`. We could even allow the ```...``` syntax along the way.

Edited Jun 13, 2018 by Raphaël Rieu-Helft
To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking