Skip to content

fluent: consider deprecating and then removing Reflect APIs in favor of bindnode #337

Open
@mvdan

Description

@mvdan

bindnode is also implemented via reflection, it has more features (such as using custom Go types), and I believe it supports all the features that these fluent reflect APIs provide.

We should probably deprecate the fluent reflect APIs (n.b. just the "reflect" family, not all of the fluent package) in favor of bindnode, and remove them a couple of releases later.

Before doing any of this, we could be nice and search across PL for users of these APIs, and submit PRs to move them to bindnode.

When we deprecate, we can then also close #212.

cc @warpfork @rvagg

Metadata

Metadata

Assignees

No one assigned

    Labels

    P3Low: Not priority right now

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions