| | |
| https://ziglang.org/documentation/master/#Pointers | |
| *T - single-item pointer to exactly one item. | |
| Supports deref syntax: ptr.* | |
| [*]T - pointer to unknown number of items. (eq. of *T in C) | |
| Supports index syntax: ptr[i] | |
| Supports slice syntax: ptr[start..end] | |
| Supports pointer arithmetic: ptr + x, ptr - x |
calendarID from cal.csv can be used at path param in
https://developers.google.com/calendar/v3/reference/calendars/get
https://developers.google.com/calendar/v3/reference/events/list
The following is the notes I took years ago on the book Ultralearning by Scott Young. The bombastic title and promise to learn virtually anything quickly makes it sound as if its the typical marketing-powered fluff-filled nonfiction book stores are overflowing with, but something about this book stuck with me. After finishing it I quickly went back and wrote these thoughts down. While I don't follow his layout of plans regularly, I have used it to guide a lot of my own self education.
I've successfully utilized it when I needed to refresh on mathematics for my Master's degree (a host of skills that atrophied sigificantly for the dozen years between undergrad and the masters). I've also used it to self-study subjects like Robotics and Deep Learning (though I did decide in the end to go for the Master's accreditation).
I share it here with hopes that someone finds it useful.
This document provides a comprehensive guide on using the tracing::instrument macro in Rust. It covers the basics of the tracing crate, the purpose and functioning of the instrument macro, and best practices for its effective use in software development.
-
Overview: The
tracingcrate is a collection of Rust libraries for application-level tracing and asynchronous diagnostics. It provides a framework for collecting structured, event-based diagnostic information. Theinstrumentmacro, specifically, is a part of this crate. It automatically attaches context-specific information to logs, such as function arguments and return values, making it easier to track the flow and performance of the code. -
Purpose: The primary purpose of the
tracing::instrumentmacro is to aid in diagnostics and performance analysis. By annotating functions with this macro, developers can automatic