Add Clarity support

[agraebe]

Adding support for the Clarity Smart Contract language

Checklist:

• I am adding a new language.
  • The extension of the new language is used in hundreds of repositories on GitHub.com.
    • Search results for .clar extension
  • I have included a real-world usage sample for all extensions added in this PR:
    • Sample source(s):
      • Proof of Transfer consensus mechanism
      • Bitcoin Naming Service
      • Cost voting mechanism
    • Sample license(s): GPL-3.0 (all)
  • I have included a syntax highlighting grammar
  • I have updated the heuristics to distinguish my language from others using the same extension.

[lildude]

Usage isn't quite there yet:

Total files found: 1315
Unique public user/repos: 170
Unique owners: 117

[Alhadis]

Unique public user/repos

I realised earlier that saying "unique user/repos" is redundant, since a repository can't logically be owned by more than one user. Perhaps we can simplify our docs by counting users only?

[lildude]

Please address the test failure

[lildude]

I realised earlier that saying "unique user/repos" is redundant, since a repository can't logically be owned by more than one user. Perhaps we can simplify our docs by counting users only?

I've been using this to allow for a bit more flexibility as it allows users to have multiple repos, with the added unique users hinting at if there's a few users disproportionately contributing to the total repos.

[agraebe]

Usage isn't quite there yet:

Total files found: 1315 Unique public user/repos: 170 Unique owners: 117

Thanks for sharing! Is there a way to run this analysis on my end? I tried Harvester but hitting this issue: Alhadis/Harvester#17 (comment)

[agraebe]

@lildude could you please run the analysis again? and if you could help me with guidance on how to run it on my own, that'd be great.

thanks!

[lgalabru]

@lildude in parallel, we're also working on updating the Clarity LSP (https://github.com/hirosystems/clarity-lsp), to make it compatible with https://github.dev, and being on linguist would already be a great addition!
Any change you could give us the new numbers? Thank you so much for your help.

[lildude]

I'm not performing reviews of PRs or popularity checking until I've got the time to start working on the next release (likely to be in early Feb at the earliest).

[jdbender66]

@lildude Any update on the total count of Clarity :user/:repo? We had a lot of activity over the holidays and think we should be past the 200 threshold needed for inclusion in Linguist.

[lildude]

Approving this based on the temporary requirements detailed in #5756

[lildude]

Whoops, looks like we've got CI failures that need addressing first.

[lildude]

Whoops, looks like we've got CI failures that need addressing first.

Fixed it.

[jdbender66]

@lildude Hey there! Thanks so much for approving these changes and merging Clarity into Linguist.

Any idea if/when Clarity will be picked up by some of Github's features?

Wondering if Clarity will show up in the language dropdown for advanced search:

Also, in the code breakdown sidebar when viewing a repo:

Thanks! Curious if there is delay with automation.

[lildude]

Nothing will appear on GitHub until I've made a new Linguist release which I'll probably do next week or early the week after, depending on my workload.

This will however only affect language classification, syntax highlighting and the colourful bar in the sidebar. Search will only gain support when go-enry is updated to pull in the changes in the next Linguist release and then you'll need to wait for our Search team to update the version of go-enry Search uses to pull in those changes.