Quentin Bernet
Quentin Bernet
Cyclic reference error when refering to an implicit parameter from another implicit parameter's type
Might be related to: https://github.com/lampepfl/dotty/issues/17242 https://github.com/lampepfl/dotty/issues/17224
Cyclic reference error when refering to an implicit parameter from another implicit parameter's type
This can also be minimized like so: ```scala class myAnnot(s: Int) extends scala.annotation.Annotation given String @myAnnot(summon[Int]) = "" // error: Cyclic reference involving val given_String ``` In that case it...
We seem to be having a similar issue: We get this error on that block: ``` possibly more than one element returned by an expression in a FILTER clause Hint:...
I cannot copy it in full, but here are the fields being used/queried: ``` type User { single organization: Organization; apiKey: uuid { constraint exclusive; }; access policy ApOne allow...
I also found a query which has neither `filter` not `filter_single` (and still shows the warning), so this is definitely an access policy issue With that query, the generated edgeQL...
> I am in favor of both ideas. > > Small correction: It would be `ab_list2: "[" __separated{("a" | "b"), ","} "]"` Well spotted, I updated it ! (Now it's...
Oh I forgot to add, if I change something about type `B`, on `gel migration create` I either get the above, or: ``` did you create object type 'default::B'? >...
@upview I'll let you look into it
Hello, This is a type of issue I've been thinking about a lot since discovering the many problems with java-style inheritance I've come to view the following as my ideal...
## explicit `@override` proposal Instead of having an isolated `provides`/`resolutions` block at the top, overriding methods are declared with an `@override` annotation which contains the identifier of the overridden method....