Fix operator conflict

[Giulero]

This pull request should fix #2067.
cc @GiulioRomualdi @traversaro

[update-docs]

Thanks for opening this pull request! The maintainers of this repository would appreciate it if you would update the release notes by adding a file in doc/release/<target_branch>, based on your changes.

[CLAassistant]

All committers have signed the CLA.

[PeterBowman]

Does the removal of said operator affect in any way the LogStream counterpart, i.e. is it still correctly displaying std::vectors?

yarp/src/libYARP_os/src/yarp/os/LogStream.h

Lines 224 to 230 in 13d2bc8

	template <typename T>
	inline LogStream& operator<<(const std::vector<T>& t)
	{
	stream->oss << t;
	stream->oss << ' ';
	return *this;
	}

[GiulioRomualdi]

Hi @Giulero checking the CI seems that function you removed is widely used in yarp

[Giulero]

@PeterBowman thank you for pointing this out! @GiulioRomualdi, indeed. The removal seems quite harmful.
@traversaro @drdanz how do you suggest to proceed?

[PeterBowman]

I think that pasting the body of the deleted function into LogStream::operator<<(const std::vector<T> &) should make CI happy.

[drdanz]

@drdanz how do you suggest to proceed?

@PeterBowman suggestion is probably the best option

[drdanz]

Also I believe that instead of moving the implementation in Types.h might not be needed after moving the implementation...

[traversaro]

Sorry for the late response. I totally agree with @drdanz and @PeterBowman , the problem that caused #2067 is adding new operators in the std namespace, adding new operators for the classes in YARP is totally fine.

[drdanz]

Closing this in favour of #2548