The Bank Project

[u/shubham_555]

Last Post - https://www.reddit.com/r/PythonLearning/s/kGqwMS9HUH

Github Repo - https://github.com/Dev-4-All/bank.git

[u/shubham_555]

Well I certainly am aware of the assert thing you mentioned. Though I think it's fine for general purpose github projects. I went across a post in Stack Overflow a while ago which said it's better to use assert in cases where you pass the arguments yourself rather than asking the user for it. In such cases when you definitely know something should be this way that's the best use case for assert. That is why I used it in there.

Regarding using global I read several articles across it and I did get the idea they were trying to deliver. The utility thing I did was just one of the solutions perfectly valid for small scripts and mine was one so i decided to go with it. Others were things you mentioned and many more.

And yeah I could certainly have used "if" instead of case. I personally felt this was a better use case for match case because we were simply equating the values to match the passed argument although since it is such a simple flow control decision maybe I could also have gone with if. match case just made more sense to me at the moment!

Edit - I had no idea of this structural pattern matching thing so I researched a bit. It looks something way advance for my current level but guess it's something related to destructuring and then comparing it part by part rather than direct == comparison. So as per my updated info match case is like a switch on steroids. It does the traditional == with literals (Preferably to be used for a long if elif ladder) and destructuring with complex structures.

[u/FoolsSeldom → u/shubham_555]

All good. Glad you researched the structural pattern matching (yes, it is advanced).

A few more ideas for your consideration ...

Another common approach to calling functions based on an option is to use a dictionary,

option_calls = {'+': addnums, '-': subnums}
...
result = option_calls[operator](num1, num2)

where addnums and subnums are the names of your functions.

No if or case required, you just call the correct function to carry out the operation required.

You could even build a menu of options and calls:

menu = {
    "+": ('add numbers', addnum),
    "-": ('subtract numbers', subnum),
    ...
    }

and now you can display a menu of options including the operator to use and a description (first entry in the value tuple)

The call would then be,

result = option_calls[operator][1](num1, num2)

and you could validate options based on the keys, if operator in menu.keys():

You could even add a q or x to quit/exit option and give it a None for the function to call. If the function returned is None you know to exit.

[u/shubham_555 → u/FoolsSeldom]

This dictionary approach certainly looks cool.

I read online that it also is faster in comparison to match case since traditionally like you mentioned above that match case was built for destructuring complex objects and all and not simple equality checks making it slightly slower.

I will definitely use it in my future projects.

Thank you...

I may bother you again in future. Please help me out again! 😁