D: parse user-defined attributes

[ntrel]

Hi,
I'm working on porting the remaining Geany D parser changes to ctags.

UDAs can precede a declaration or come after a function parameter list.
https://dlang.org/spec/attribute.html#uda

• I'm not sure if all the lines in expected.tags starting with !_TAG_ should be there. Please let me know if there's a switch I should be using.
• I'm not sure if I add a changelog entry somewhere, please let me know.

[codecov]

Codecov Report

Patch coverage: 100.00% and no project coverage change.

Comparison is base (39a0172) 82.82% compared to head (2f6af94) 82.83%.

❗ Current head 2f6af94 differs from pull request most recent head 9f54e5d. Consider uploading reports for the commit 9f54e5d to get more accurate results

Additional details and impacted files

@@           Coverage Diff           @@
##           master    #3701   +/-   ##
=======================================
  Coverage   82.82%   82.83%           
=======================================
  Files         226      226           
  Lines       54752    54754    +2     
=======================================
+ Hits        45351    45353    +2     
  Misses       9401     9401           

Impacted Files	Coverage Δ
parsers/c-based.c	80.62% <100.00%> (+0.03%)	⬆️

☔ View full report in Codecov by Sentry.
📢 Do you have feedback about the report comment? Let us know in this issue.

[masatake]

A minor request; could you change the commit header to "D: parse user-defined attributes"?

[masatake]

You can remove all '!_' tags from the expected.tags.

[masatake]

I would like you to split the commit into two.

The new commit #1 is for just changing the function name. The commit header may be "Java,refactor: Rename parseJavaAnnotation() to parseAtMarkStyleAnnotation()".

In the new commit #2, add D specific changes using parseAtMarkStyleAnnotation().

[ntrel]

@masatake Thanks, I've done that except the commits are in opposite order. I hope that's OK (wasn't sure how to do it the other way with git).

[masatake]

Thank you for updating.

@masatake Thanks, I've done that except the commits are in opposite order. I hope that's OK (wasn't sure how to do it the other way with git).

O.k. I will take over this...however, I recommend you to learn 'git rebase -i' and 'git push --force'. git rebase -i is not only useful but also ... impressive. I wonder who designed the function. Linus? I like the git features for polishing commits.