a/usaco-guide
Archived
1
0
Fork 0
Code Issues Pull requests Packages Projects Releases Wiki Activity

Update 3_WhyCpp.md

Browse source
This commit is contained in:
Darren Yao 2020-06-15 12:23:14 -07:00 committed by GitHub
parent 2204cc108e
commit e1ec975fac
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
1 changed files with 1 additions and 1 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

2
content/2_General/3_WhyCpp.md
View file

@ -233,4 +233,4 @@ Although both Python and Java receive two times the C++ time limit in USACO, thi
- Python lacks a data structure that keeps its keys in sorted order (the equivalent of `set` in C++), which is required for some silver problems.
- Java lacks features such as `#define`, `typedef`, and `auto` that are present in C++ (which some contestants rely on extensively, see "macros").
- USACO problemsetters don't always test Java solutions (and rarely Python) when setting constraints.
- USACO problemsetters don't always test Java solutions (and rarely Python) when setting constraints. Furthermore it is not guaranteed that there exists a fully working solution in Python.