Skip to content

Some operators do not follow naming convention #5366

@kexinzhao

Description

@kexinzhao

Authors of operators should follow the name convention as detailed in here.

Below is the list of ops that does not follow parameter naming convention.
It is suggested that the main author of the operator fix the issue.

People can add to this list when they find applicable cases.

  • lstm_op (attribute names does not follow snake_case) ( @qingqing01 )
  • lstm_unit_op (Input name C_prev does not follow CamelCase) ( @zchen0211 )
  • momentum_op (attribute name useNesterov does not follow snake_case) ( @sidgoyal78 )
  • pool_op (some attribute names does not follow snake_case) ( @chengduoZH )
  • pool_with_index_op (some attribute names does not follow snake_case) ( @chengduoZH )
  • recurrent_op (input/output/attr names does not follow conventions) ( @reyoung )

Metadata

Metadata

Labels

No labels
No labels

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions