-
How likely is it that the .ice Source file generation for C# will be migrated to C# Source Generators instead of MSBuild task juggling? Are there any plans?
Gulum updated
1 month ago
-
It appears the build system is currently using some other slicec-cs, not the one you've just built from sources.
-
Currently, our spans are 1-indexed to be more in line with how files are represented in editors. However, this has proven to be painful when implementing things like a language server, as the LSP prot…
-
I am getting the following errors in the dev container:
```
IceRpc.Quic.Tests test failed with 2 error(s) and 3 warning(s) (10.6s)
/workspaces/icerpc-csharp/tests/IceRpc.Conformance.Tests/T…
-
Currently, as suggested by @pepone the BuildTelemetry works via a shared custom build task that gets called by the `IceRpc.Slice.Tools` and `IceRpc.Protobuf.Tools`. I think this approach is good for n…
-
The current process when writing an IceRPC+Slice application is:
a) describe your Slice interfaces in a Slice file (.slice)
b) generate code from these Slice files with the Slice compiler
c) wri…
-
Many languages provide a way of 'pulling in' other namespaces:
- C++ `using MyNamespace`
- C# `using MyNamespace`
- Java `import MyPackage`
- Rust `use MyModule`
Slice should also provide a fea…
-
Like @externl pointed out, we frequently use `` and `` 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…
-
Common syntax mistakes should be given dedicated error messages.
All other syntax error messages should be cleaned up to be more human readable. Right now they leak the identifiers of tokens, which…
-
> > 7\. I am pretty sure this ReadFrameAsync method executes in the critical "read loop" where we need to be really careful about not doing too much work
>
> I would open another issu…