#pragma once

#include <vector>
#include <string>
#include <string_view>
#include <optional>
#include <utility>
#include <functional>
#include <variant>
#include "process.h"

using namespace std;


class Referee {
	const bool verbose;

	Process proc;
	string refereeExecname;
	int numPlayers;

	string reftag;

	struct Features {
		// Referee supports current version of the protocol.
		bool version2;
	};
	Features features;

	void queryFeatures();

public:
	struct ReadEvent {
		int player;
		// call with the line read (no newline)
		function<void(const string&)> callback;
	};
	struct WriteEvent {
		int player;
		bool allowBrokenPipe;
		string line;
	};
	struct GamelogEvent {
		int player;
		string line;
	};
	struct EndEvent {
		vector<int> scores;
	};
	struct ErrorEvent {
		int player;
		string message;
	};
	using Event = variant<ReadEvent, WriteEvent, GamelogEvent, EndEvent, ErrorEvent>;

	Referee(bool verbose, const string_view execname, const vector<string> &players);
	~Referee();

	Event nextEvent();

	// Kills the referee process
	void terminate();
};

/*
Referee protocol:

At startup, the referee should write a number of lines to stdout of the form
'feature <name>', indicating that the referee supports the feature given by
<name>. The list of features should be ended with a line containing
'feature_end'. To use the version of the protocol described here, it is
mandatory to request 'feature version_2'. For supported features and their
effect, see below.

The referee then receives a line containing the number of players in the game,
followed by that number of lines containing the players' names.

Then, the referee has the following commands available:
- 'read <player>': read a line from the player with index <player>; this line
  is written directly to the referee afterwards. The first player is 0, the
  second player is 1, etc.
- 'write <player> <line>': write a line to the player with index <player>.
- 'writemaybe <player> <line>': write a line to the player with index <player>,
  without considering a broken pipe error to be fatal. This is useful for Quit
  messages because codecup players tend to exit before getting a formal Quit
  sometimes.
- 'gamelog <player> <line>': write a line in the game log indicating that the
  player with index <player> made the move given by <line>.
- 'end <score> <score> ...': signify that the game has ended. The final scores
  of the players are given after 'end'. These scores should be given as a
  space-separated list of integers, as many as there are players.
- 'error <player> <message>': indicate that the player with index <player> has
  produced erroneous output. This ends the game. The <message> will be
  presented to the user and written to the gamelog.

FEATURES
Currently, the following features are supported:
- 'version_2': must be used by all referees.
*/