You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Like @externl pointed out, we frequently use <c> and <code> xml tags in our doc comments to format something as code,
but the slice compiler just treats that like raw text. It just happens to work because it means something to C# and currently, we only support C#. We should add a real tag for code snippets into the comment language like was suggested: icerpc/icerpc-csharp#2728 (comment)
The text was updated successfully, but these errors were encountered:
How exactly would this work? And would we allow multi-line code snippets too?
I think having {@code: x+1} works fine for small inline code snippets, but I don't think it would look good over multiple lines.
(The comment parser also disallows inline tags spanning multiple lines, but we can probably relax that).
The downside is that's kind of unergonomic.
We could also just support standard markdown code syntax like: `x+1` and ```x+1```
It would be more ergonomic, but would look less like how the rest of our tags work.
Not sure we need multi-line code snippets, Slice comments are copied over to the generated code, what language would you use in these snippets when targeting multiple languages?
Like @externl pointed out, we frequently use
<c>
and<code>
xml tags in our doc comments to format something as code,but the slice compiler just treats that like raw text. It just happens to work because it means something to C# and currently, we only support C#. We should add a real tag for code snippets into the comment language like was suggested:
icerpc/icerpc-csharp#2728 (comment)
The text was updated successfully, but these errors were encountered: