Müller — @foonathan Express your expectations CppCon 2023-10-03 1tc::json::parser Extract some JSON members tc nlohmann RapidJSON Boost.JSON simdjson 0 10 20 30 40 Library Time in ms fully validating expectations CppCon 2023-10-03 2(JSON) Parser design What is a parser? Jonathan Müller — @foonathan Express your expectations CppCon 2023-10-03 3Javascript Object Notation (JSON) Jonathan Müller — @foonathan @foonathan Express your expectations CppCon 2023-10-03 4Javascript Object Notation (JSON) Idea: Human-readable serialization of Javascript objects. Jonathan Müller — @foonathan Express your expectations CppCon

(case insensitive sys- tems, incompatible paths, etc). The only workaround here is to use --dry-run --json to obtain the solution and process the payload into a lockfile that can be shared with the target temporary environment first just to delete it later? Fortunately, there's a way: you can invoke conda in JSON mode and then process the output with jq. � Tip You'll need jq in your system. If you don't have "@EXPLICIT" > explicit.txt CONDA_PKGS_DIRS=$(mktemp -d) conda create --dry-run MATCHSPECS_GO_HERE --json | jq -r '. ˓→actions.FETCH[] | .url + "#" + .md5' >> explicit.txt The syntax in Windows only needs

(case insensitive sys- tems, incompatible paths, etc). The only workaround here is to use --dry-run --json to obtain the solution and process the payload into a lockfile that can be shared with the target temporary environment first just to delete it later? Fortunately, there's a way: you can invoke conda in JSON mode and then process the output with jq. � Tip You'll need jq in your system. If you don't have "@EXPLICIT" > explicit.txt CONDA_PKGS_DIRS=$(mktemp -d) conda create --dry-run MATCHSPECS_GO_HERE --json | jq -r '. ˓→actions.FETCH[] | .url + "#" + .md5' >> explicit.txt The syntax in Windows only needs

macOS Catalina). Each package has an index.json file which lists the package’s dependencies. This file resides in ~anaconda/pkgs/package_name/info/index.json. 4. Now you can find what packages depend depend on a specific package. Use grep to search all index.json files as follows: grep package_name ~/anaconda/pkgs/*/info/index.json The result will be the full package path and version of anything containing Example: grep numpy ~/anaconda3/pkgs/*/info/index.json Output from the above command: /Users/testuser/anaconda3/pkgs/anaconda-4.3.0-np111py36_0/info/index.json: numpy 1.11.3␣ ˓→py36_0 /Users/testuser/ana

(case insensitive sys- tems, incompatible paths, etc). The only workaround here is to use --dry-run --json to obtain the solution and process the payload into a lockfile that can be shared with the target temporary environment first just to delete it later? Fortunately, there's a way: you can invoke conda in JSON mode and then process the output with jq. � Tip You'll need jq in your system. If you don't have "@EXPLICIT" > explicit.txt CONDA_PKGS_DIRS=$(mktemp -d) conda create --dry-run MATCHSPECS_GO_HERE --json | jq -r '. ˓→actions.FETCH[] | .url + "#" + .md5' >> explicit.txt The syntax in Windows only needs

macOS Catalina). Each package has an index.json file which lists the package’s dependencies. This file resides in ~anaconda/pkgs/package_name/info/index.json. 4. Now you can find what packages depend depend on a specific package. Use grep to search all index.json files as follows: grep package_name ~/anaconda/pkgs/*/info/index.json The result will be the full package path and version of anything containing Example: grep numpy ~/anaconda3/pkgs/*/info/index.json Output from the above command: /Users/testuser/anaconda3/pkgs/anaconda-4.3.0-np111py36_0/info/index.json: numpy 1.11.3␣ ˓→py36_0 /Users/testuser/ana

macOS Catalina). Each package has an index.json file which lists the package’s dependencies. This file resides in ~anaconda/pkgs/package_name/info/index.json. 4. Now you can find what packages depend depend on a specific package. Use grep to search all index.json files as follows: grep package_name ~/anaconda/pkgs/*/info/index.json The result will be the full package path and version of anything containing Example: grep numpy ~/anaconda3/pkgs/*/info/index.json Output from the above command: /Users/testuser/anaconda3/pkgs/anaconda-4.3.0-np111py36_0/info/index.json: numpy 1.11.3␣ ˓→py36_0 /Users/testuser/ana

macOS Catalina). Each package has an index.json file which lists the package’s dependencies. This file resides in ~anaconda/pkgs/package_name/info/index.json. 4. Now you can find what packages depend depend on a specific package. Use grep to search all index.json files as follows: grep package_name ~/anaconda/pkgs/*/info/index.json The result will be the full package path and version of anything containing Example: grep numpy ~/anaconda3/pkgs/*/info/index.json Output from the above command: /Users/testuser/anaconda3/pkgs/anaconda-4.3.0-np111py36_0/info/index.json: numpy 1.11.3␣ ˓→py36_0 /Users/testuser/ana

macOS Catalina). Each package has an index.json file which lists the package’s dependencies. This file resides in ~anaconda/pkgs/package_name/info/index.json. 4. Now you can find what packages depend depend on a specific package. Use grep to search all index.json files as follows: grep package_name ~/anaconda/pkgs/*/info/index.json The result will be the full package path and version of anything containing Example: grep numpy ~/anaconda3/pkgs/*/info/index.json Output from the above command: /Users/testuser/anaconda3/pkgs/anaconda-4.3.0-np111py36_0/info/index.json: numpy 1.11.3␣ ˓→py36_0 /Users/testuser/ana

conda, Release 23.11.1.dev1 Package structure . bin pyflakes info LICENSE.txt files index.json paths.json recipe lib python3.5 • bin contains relevant binaries for the package. • lib contains the discussed below. Info • files – a list of all the files in the package (not included in info/) • index.json – metadata about the package including platform, version, dependencies, and build info { "arch": "platform": "linux", "subdir": "linux-64", "timestamp": 1535416612069, "version": "0.0.0" } • paths.json – a list of files in the package, along with their associated SHA-256, size in bytes, and the type