Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Sign in / Register
  • GHC GHC
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 5,246
    • Issues 5,246
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
  • Merge requests 570
    • Merge requests 570
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
    • Test Cases
  • Deployments
    • Deployments
    • Releases
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Code review
    • Insights
    • Issue
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • Glasgow Haskell CompilerGlasgow Haskell Compiler
  • GHCGHC
  • Issues
  • #19626
Closed
Open
Issue created Apr 01, 2021 by syd@cs-syd.eu@kerckhove_tsContributor

Long-form names for RTS options

Summary

The GHC RTS has a lot of options. Most of them only have short-form names, so that you cannot tell what they do if you don't know what the letters mean:

This invocation:

+RTS -H2G -A32M -xc -RTS

is a magic incantation

This example proposed version:

--sugested-heap-size 2G --allocation-area-size 32M --dump-stack-traces-on-exception

is self-evident.

The short options would still be available in case you care about typing a few more characters (and for backward compatibility).

Proposed improvements or changes

Give each RTS option a long-form name along with the short-form name.

Edited Apr 01, 2021 by Matthew Pickering
To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking