Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Convention for name of variables to represent numbers

See original GitHub issue

This issue is partially related to https://github.com/chainer/chainer/pull/7871. In Chainer, there are some ways to represent numbers.

n_{prural noun}: https://github.com/chainer/chainer/blob/master/chainer/links/rnn/n_step_lstm.py#L119
n_{singular noun}: https://github.com/chainer/chainer/blob/master/chainer/datasets/sub_dataset.py#L233
num_{prural noun}: https://github.com/chainer/chainer/blob/master/chainer/training/extensions/_snapshot.py#L77

(It seems most examples using n_{prural_noun}.)

I think it would be better to unify the way for them. (Determining the policy would help to keep consistency, I think.)

Issue Analytics

State:
Created 4 years ago
Comments:17 (12 by maintainers)

Top GitHub Comments

1reaction

sameshlcommented, Sep 3, 2019

@himkt I have not been able to contribute from about a week or so due to a laptop issue. I am still fixing my laptop :sweatsmile: . I would be happy if you could take this up and thanks for keeping up with me despite me not able to contribute!

1reaction

sameshlcommented, Aug 10, 2019

Cool 👍 . Just ping here when the policy is decided.