why do we need receive() function at all, why not use fallback() everywhere?

[SrikanthAlva]

From the flowchart shown at https://youtu.be/gyMwXuJrbJQ?t=19457.

This clearly indicates that if we do not write receive() function and use only the fallback() function, all calls will be routed through the fallback() function.

This brings me to the question, why do we need receive() function at all, why not use fallback() everywhere?
In what scenario will there be a need to use both receive() and fallback() functions in the code?

[cromewar]

Hello @SrikanthAlva

The case scenario as shown on the image is for functions like send() or transfer()

[PatrickAlphaC]

Long story short:

You may want your contract to act differently when you are sent ether vs sent data. You could 100% always use the fallback, but it'll be a little more gas efficient if you do have different functionality to have both. Otherwise, you'd have to do some data validation in your fallback to check for data.

[PatrickAlphaC]

Let us know if this solves your issue.

[SrikanthAlva]

Thank You so much @PatrickAlphaC this helps a lot