Skip to content

GitLab

  • Menu
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 4,869
    • Issues 4,869
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
  • Merge requests 456
    • Merge requests 456
  • 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 Compiler
  • GHCGHC
  • Issues
  • #19437
Closed
Open
Created Feb 25, 2021 by Hécate Moonlight@KleidukosDeveloper

[Discussion] Linting the RTS code

While looking at @bgamari's commment on !5119 (comment 334267) I realised we could try and automate the detection of bad citizens in our RTS C code. Tools like cpplint or oclint exist and could be used to warn us about those things. This feels like a better solution than having to re-define those functions like this:

#define usleep(_) #pragma error("NO!")

Candidates for exclusion could be

  • usleep
  • assert (in favour of ASSERT)
Edited Feb 25, 2021 by Hécate Moonlight
To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking