ENH: Implemented optional initializer for pd.concat (#40820)
- [x] closes #40820 
- [x] tests added / passed (passed on azure checks)
- [x] Ensure all linting tests pass, see [here](https://pandas.pydata.org/pandas-docs/dev/development/contributing.html#code-standards) for how to run them
- [x] whatsnew entry

A proposed solution for issue #40820, to accept an optional argument ``initializer`` which allows for concatenating empty sequences and return the object passed to initializer -- which can be useful for cases where users are running pd.concat on sequence variables which might potentially be empty -- and would like the result of the concatenation to be initialized to an empty Series/DataFrame

The new argument is made optional, and the ValueError is still thrown for cases where the ``initializer`` is not specified -- this should maintain expected behaviour / backward compatibility 

As stated in https://github.com/pandas-dev/pandas/issues/40820#issuecomment-834604151, I don't think `concat` should be responsible for determining the return type for an empty input. > @yushao2 sympathize with the issue. we don't anything like this and don't think have this magically just work is a good idea. not to mention adding complexity.

no worries, I will rescind the PR :) cheers