An example related to question on Twitter https://twitter.com/drewdaraabrams/status/1359933543619547137
Try curl https://entreprise.data.gouv.fr/api/sirene/v1/full_text/MONTPELLIERAIN
Among result, look at
"total_results": 161,
[ | |
{ | |
"name": "Afghanistan", | |
"dial_code": "+93", | |
"code": "AF" | |
}, | |
{ | |
"name": "Aland Islands", | |
"dial_code": "+358", | |
"code": "AX" |
An example related to question on Twitter https://twitter.com/drewdaraabrams/status/1359933543619547137
Try curl https://entreprise.data.gouv.fr/api/sirene/v1/full_text/MONTPELLIERAIN
Among result, look at
"total_results": 161,
Other people's projects:
My projects (tutorials are on my blog at http://maxoffsky.com):
if [ ! -z "${IDE}" -a "${IDE}" == "AndroidStudio" ]; then | |
cd $OLDPWD; | |
fi |
For the every-day programmer who needs to get shit done instead of fighting type errors.
If your application deals with times in any meaningful way, you should probably want to actually store time_points and durations and what-not; chrono has a pretty rich vocabulary for talking about time-related concepts using the type system. However, sometimes you just need to do something simple, like timing how long something takes, which is where chrono becomes overly complex, hence this cheat sheet.
All examples will assume #include <chrono>
.
This is inspired by A half-hour to learn Rust and Zig in 30 minutes.
Your first Go program as a classical "Hello World" is pretty simple:
First we create a workspace for our project:
Lecture 1: Introduction to Research — [📝Lecture Notebooks] [
Lecture 2: Introduction to Python — [📝Lecture Notebooks] [
Lecture 3: Introduction to NumPy — [📝Lecture Notebooks] [
Lecture 4: Introduction to pandas — [📝Lecture Notebooks] [
Lecture 5: Plotting Data — [📝Lecture Notebooks] [[
#!/usr/bin/env ruby | |
# encoding: UTF-8 | |
# EXAMPLE | |
# | |
# { | |
# "kind": "Event", | |
# "apiVersion": "audit.k8s.io/v1", | |
# "level": "Metadata", | |
# "auditID": "f6618a15-8e4f-4f82-95b3-7592ed544eb9", |