From c4c543ed1d3be8a239bbf6deb1b21602c836b630 Mon Sep 17 00:00:00 2001 From: Chris Kipp Date: Sun, 15 Jan 2023 09:11:54 +0100 Subject: docs: clarify @storageclass in CONTRIBUTING docs This is just a tiny change that was in reference to https://github.com/nvim-treesitter/nvim-treesitter/pull/4153#discussion_r1070276800. The basis is that `@storageclass` should only be used unless it's actually affecting storage in memory. There are further conversations about this in the following places: - https://github.com/nvim-treesitter/nvim-treesitter/pull/3648#issuecomment-1279923861 - https://github.com/nvim-treesitter/nvim-treesitter/pull/3648#issuecomment-1291624844 --- CONTRIBUTING.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index 34131d446..d2367dd03 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -161,7 +161,7 @@ effect on highlighting. We will work on improving highlighting in the near futur @type.definition ; type definitions (e.g. `typedef` in C) @type.qualifier ; type qualifiers (e.g. `const`) -@storageclass ; visibility/life-time modifiers +@storageclass ; life-time modifiers that affect storage in memory @attribute ; attribute annotations (e.g. Python decorators) @field ; object and struct fields @property ; similar to `@field` -- cgit v1.2.3-70-g09d2