Skip to content

ft-lambda: handle generic types #2

Description

@lalmeras

Current behavior: when target type is generic, we use plain old inner binding classes.

We should move to lambda expressions.

Two cases must be handled:

  • raw type; binding to a private Map field; for example
  • anonymous constrained type; binding to a private Map<? extends K, V> or private Map<K, ? extends K> field or private Map<? extends K, ? extends V> field
  • anonymous unconstrained type; binding to a private Map<?, V> or private Map<K, ?> field or private Map<?, ?> field

For raw type, we need to build a custom TypeRawBindingPath<R, P, T> extends AbstractBinding<R, P, T, Type> as a binding base class.

Not sure if constrained and unconstrained types are really different cases.

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions