The same object as input and output in Python - good or bad practice? [closed]

Question

Closed. This question is opinion-based. It is not currently accepting answers.

Want to improve this question? Because this question may lead to opinionated discussion, debate, and answers, it has been closed. You may edit the question if you feel you can improve it so that it requires answers that include facts and citations or a detailed explanation of the proposed solution. If edited, the question will be reviewed and might be reopened.

Closed 5 years ago.

Improve this question

I was just wondering if this is an clean way of writing code - if you define the same name of a variable (and precisely for a dictionary) that you use as an input and an output of some function e.g.:

my_dic = {}
my_dic = someFunction(my_dic,otherVariables)
**doing other things with my_dic **

The function someFunction only is meant to update the dictionary my_dic, so preferably the output should be the input but updated. Is this a safe way of coding? or would that result in some possible bugs?

WangGang · Accepted Answer · 2020-03-10 14:51:03Z

2

This should not result in any bugs in your program if you are just trying to update the dictionary using a function.

answered Mar 10, 2020 at 14:51

WangGang

5333 silver badges15 bronze badges

Sign up to request clarification or add additional context in comments.

Collectives™ on Stack Overflow

The same object as input and output in Python - good or bad practice? [closed]

1 Answer 1

Comments

Hot Network Questions

Collectives™ on Stack Overflow

1 Answer 1

Comments

Related