While using namespace std; may have some benefits, it has some downsides too. Therefore the decision whether or not to use the namespace should be left to the person writing the bot. However, when you put using namespace std; in a header at global scope, that means that you make that decision for the user of the library, as they can't remove this statement.
The fix for this would be to move the using namespace std; into the kit namespace, so this
using namespace std;
namespace kit {
// ...
}
would become this
namespace kit {
using namespace std;
// ...
}
This would be a breaking change though, but given that it's quite early in the competition, I think this is acceptable.
While
using namespace std;
may have some benefits, it has some downsides too. Therefore the decision whether or not to use the namespace should be left to the person writing the bot. However, when you putusing namespace std;
in a header at global scope, that means that you make that decision for the user of the library, as they can't remove this statement.The fix for this would be to move the
using namespace std;
into thekit
namespace, so thiswould become this
This would be a breaking change though, but given that it's quite early in the competition, I think this is acceptable.