generic | A code generation tool to enable generics in go | Generator Utils library

A functional approach would be (but probably not clean)

See microsoft/TypeScript#43667 for a canonical answer. This is a design limitation of TypeScript.

As you might be aware: in TypeScript's structural type system, Child is a subtype of Base even though it is not explicitly declared as such. So every value of type Child is also a value of type Base (although not vice-versa). That means Child | Base is equivalent to Base... although the compiler is not always aggressive about reducing the former to the latter. (Compare this to the behavior with something like "foo" | string, which is always immediately reduced to string by the compiler.)

Subtype reduction is often desirable, but there are some places where Child | Base's behavior is observably different from Base's, such as excess property checks, IntelliSense hinting, or the sort of unsound type guarding that happens with the in operator. You haven't shown why it matters to you that you are getting a Base as opposed to a Child | Base, but presumably it's one of these observable differences or something like it.

My advice here is first to think carefully about whether or not you really need this distinction. If so, then you might consider preventing Base from being a subtype of Child, possibly by adding an optional property to it:

Three things come immediate to mind.

The first is nothing to do with your question but CouponRepository should not have its own member for _couponApiDBContext it has access to the base class TContext - that's the whole point of having it generic in the first place.

The second is that you are specializing IRepository with RedeemCoupon method in ICouponRepository - so you have zero chance of registering an open generic type and just expecting DI to know what actual interface you're after.

You're left with removing this AddTransient(typeof(IRepository<>), typeof(Repository<,>)) - it's pointless as DI cannot instantiate an abstract class anyway, and that is the root cause of your error message and you should register AddTransient() and request ICouponRepository where you need it - you cant ask for IRepository as that will not have your RedeemCoupon method which I assume you need.

You should use http://localhost:55643/api/ShipmentsStatus/getShipmentsStatusJSON or change [Route("getShipmentsStatusJSON")] to the appropriate API method name

Your immediate issue is that T: GarbageBin<'a, 'b> where 'a and 'b are parameters of create_bin_with_rubbish and must therefore outlive calls to that function—but the actual lifetimes passed to T::new are only internal to the function and do not therefore satisfy those bounds.

Instead of parameterising create_bin_with_rubbish with lifetimes 'a and 'b, one way to resolve this would be to use instead an HRTB (higher-ranked trait bound):

you should run your Web API from this address http://localhost:18084/Employee

Assuming what I mentioned in my comment on your question, the fix is just to simplify your FieldWithConfidence type significantly. Right now it is trying to add a number of additional levels of structure beyond what you seem to want. Here is a version of that type that works as I think you intend:

AllTime_ is a List so each element is one single string not again a List so Add has a single string as parameter - you are trying to give it an entire list.

Only problem is the List is redefined and the size of the list changes

This doesn't sound quite right either ;) What happens is you overwrite the list. The size should be the same since you Select the same amount of items. What you rather want though is combining both results into one single list.

You are probably looking for AddRange

This might help you: