Skip to content

Improve restrictions on attributes/operations when maplike/setlike are used #49

Open
@bzbarsky

Description

@bzbarsky

Two changes:

  1. Use of maplike/setlike should not affect static attributes/operations (but should affect constants, as it does now, since those go on the proto too).

  2. The mutator methods (clear, add, set, delete) should not be allowed to shadow a method on an inherited interface. But having them on the interface itself or its consequential interfaces should be OK (as now) and just inhibit autogeneration of the method.

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