We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Possible implementation for a code executor would be a pipeline architecture:
(user program ) + --> code executor ---> (program output/err) (qn's .in files) ---------------------------------------------------------------- (program output/err) + --> verifier ---> (solve status + program output/err) (qn's .out files)
Then all we need to do is to supply the backend with the user's program and its metadata, the .in files and .out files
.in
.out
The text was updated successfully, but these errors were encountered:
Isaaclhy00
No branches or pull requests
Possible implementation for a code executor would be a pipeline architecture:
Then all we need to do is to supply the backend with the user's program and its metadata, the
.in
files and.out
filesThe text was updated successfully, but these errors were encountered: