-
Follow up to https://github.com/dagger/dagger/pull/6254
You can't yet use types from the core api like `Container`/`Directory`/etc. to implement a given interface.
You also can't implement core …
-
Files that export types and/or interfaces that are used in the codebase are marked as unused by the plugin.
Here's a minimal repro: https://github.com/MathiasWP/vite-plugin-unused-code-types-and-in…
-
Some interfaces defined in the package support only comparable types.
sets.Set
```go
type Set[T comparable] interface {
Add(elements ...T)
Remove(elements ...T)
Contains(elements ...T) bool…
-
the consuming application is passing a data structure like this into the `` `src` prop to support "live stream" asset types.
```
type Source = {
type: string;
streamName: string;
subscri…
-
It's important to get it right, for when exporting with `ex_doc`.
-
Hello!
I expect this to work:
```
export type FinalType = GenericType
export type GenericType = T
```
but it isn't recognizing type params, all my types with generic type implementation are …
-
Consider the following interface where I have a method whose other input types are known in context, but those types are different in general and do not share a common supertype outside of `Any`:
`…
-
## 🪤 Context
Right now it's only possible to associate types with a service call response manually (per-call), or have it hard coded in type-writer.
It'd be nice if there were an interface that…
-
I encountered an error during the compilation of the demo, as shown below:
error[E0308]: mismatched types
--> gateway/src/interface/server.rs:108:38
|
108 | *resp.status_mut() = status;
| -----…
-
Hello!
Working on an integration with the vezgo-sdk (currently v1.1.0) on a TypeScript project. Running into a bit of frustration as, although the types used by the sdk are defined, they are not ex…