TypeSpec: new parser

[iaalm]

Add parser for TypeSpec

Test passed with make units LANGUAGES=TypeSpec

[codecov]

Codecov Report

Attention: Patch coverage is 98.06452% with 6 lines in your changes missing coverage. Please review.

Project coverage is 85.95%. Comparing base (7dbc4db) to head (846da8d).
Report is 2 commits behind head on master.

Files with missing lines	Patch %	Lines
parsers/typespec.c	98.06%	6 Missing ⚠️

Additional details and impacted files

@@            Coverage Diff             @@
##           master    #4243      +/-   ##
==========================================
+ Coverage   85.89%   85.95%   +0.05%     
==========================================
  Files         245      246       +1     
  Lines       63149    63459     +310     
==========================================
+ Hits        54240    54544     +304     
- Misses       8909     8915       +6     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[masatake]

Well written. Thank you.
Could you add the name of the new parser to docs/news/HEAD.rst?

I think we can simplify the code with "cork API",
See https://docs.ctags.io/en/latest/internal.html#cork-api

I will show you how to apply the CORK API to your parser in the next comment.

[masatake]

Let's use CORK API.
See the latest two commits at https://github.com/masatake/ctags/commits/tsp-20250509/ .

[masatake]

Shouldn't we extract v2024_05_01_preview ?

NYY-choice.

[iaalm]

Yes, I have thinked about this. I can do in another PR. BTW, @masatake , could you suggest TypeSpecKinds for this type? I don't find much examples of such kind.

[masatake]

As far as reading https://typespec.io/docs/language-basics/enums/, the enum in TypeSpec is not so different from that in C. So we can reuse what the C parser defines.

$ ./ctags --list-kinds-full=C | grep enum
e       enumerator yes     no      0      C      enumerators (values inside an enumeration)
g       enum       yes     no      0      C      enumeration names

e,enumerator,enumerators (values inside an enumeration) looks suitable here.

[masatake]

We should refer to TypeScript instead of C.

$ ./ctags --list-kinds-full=TypeScript | grep enum
e       enumerator yes     no      0      NONE   enumerators (values inside an enumeration)
g       enum       yes     no      0      NONE   enums

TypeScript also uses g.

[masatake]

I'm interested in extracting imported items and usinged items.
I will work on them after merging this pull request.

#3906
#2428

[masatake]

We can fill inherits: field of interfaceA: with InterfaceB.
NYY-choice.

Filling such a field makes your work applicable to broader use cases.

Here is an example of C++.

$ cat /tmp/foo.cc 
class A: B {
	int x;
};
$ ./ctags -o - /tmp/foo.cc
A	/tmp/foo.cc	/^class A: B {$/;"	c	file:
x	/tmp/foo.cc	/^	int x;$/;"	m	class:A	typeref:typename:int	file:
$ ./ctags --fields=+i -o - /tmp/foo.cc
A	/tmp/foo.cc	/^class A: B {$/;"	c	file:	inherits:B
x	/tmp/foo.cc	/^	int x;$/;"	m	class:A	typeref:typename:int	file:
$ ./ctags --fields=+i -o foo.tags /tmp/foo.cc
$ ~/bin/querytags --tag-file foo.tags class-hierarchy  A
  A
   B

[iaalm]

Yes, I can do it in another PR

[masatake]

My reviewing log: These are good. They align with the kinds of TypeScript.

[masatake]

Thank you for updating.

Could you add the name of the new parser to docs/news/HEAD.rst?

[masatake]

Thank you for updating.

Could you add the name of the new parser to docs/news/HEAD.rst?
Please remove whitespace in input.tsp

[masatake]

Thank you very much.