I hereby claim:
- I am arkgil on github.
- I am arkgil (https://keybase.io/arkgil) on keybase.
- I have a public key ASBTqq_sjsQK5MbWQfsOj2gNKbKWJO5GXzcuAjknnjGLXgo
To claim this, I am signing this object:
| defmodule STask do | |
| @doc """ | |
| Constructs a stream of numbers which | |
| are worth checking if they divide n. | |
| By jumping by 2 and 4 we filter out | |
| obvious candidates. | |
| """ | |
| def divisors_stream(n) do | |
| Stream.unfold({4, 7}, fn | |
| {_, number} when number >= n -> |
| OUT_NAME = | |
| CC = gcc | |
| FLAGS=-Wall -Wpedantic -std=c11 | |
| SRC_DIR = src | |
| OBJ_DIR = build | |
| INC_DIR = headers | |
| LIBS = |
I hereby claim:
To claim this, I am signing this object:
| -module(task). | |
| -export([async/1, async/3]). | |
| -export([await/1, await/2, await/3]). | |
| -opaque t() :: #{tpid := pid(), tref := reference()}. | |
| -type await_opts() :: [kill]. | |
| -export_type([t/0]). | |
| -export_type([await_opts/0]). |
In this document we'll try to come up with the glossary for the Telemetry.Metrics project.
In order to create a glossary, it's beneficial to look at how various metric systems call different entities. Note that this comparison aims to highlight only these differences related to data model and metric types.