#scopes

2025-04-15

Sunday morning. Dayton, Tennessee. This was the town in which the famous Scopes trial (Darrow vs. Bryan) was held

#Dayton #Tennessee #Scopes #Darrow #Bryan #Gothic #undefined #photography #DorotheaLange

loc.gov/pictures/item/20177630

A black and white photograph depicting a scene outside of a church, likely taken during the early to mid-20th century. The building features Gothic architectural elements such as pointed arch windows and a steeple with a weather vane at its peak.

In front of the church stands an old-fashioned sedan parked on a street adjacent to a paved sidewalk where several people are congregating near steps leading into the church entrance. There's a woman, possibly in her 30s or early 40s wearing a flowing white dress with floral patterns and another older woman beside her; both appear happy.

Two men in suits stand by the car—one smoking—and two women also dressed in light-colored dresses are seen on the sidewalk. The attire of everyone is indicative of mid-20th-century fashion, suggesting this might be Sunday morning or a special event like church service attendance.

Various vegetation and shrubs adorn what looks to be an urban environment with paved roads indicating it's not rural. A watermark text overlay reads "Dorothea Lange - National Photo Company," which indicates the photographer who captured this moment in history as well as associated archives for additional information about her work during that era, including coverage of important events such as The Scopes Trial held in Dayton, Tennessee—a town famous for its courtroom drama involving evolution debates.
2025-02-06

Your app shouldn't need full Google access to check calendar availability.

WorkOS AuthKit now supports custom OAuth scopes for Google & Microsoft integrations 🔑

#auth #security #oauth #scopes

2024-12-15

tbh it's slightly more than that

#scopes #noir

Scopes² Compiler Pipeline

                    user ➡ text (.sx)
                               ⬇
	        token stream ⬅ lexer
                    ⬇	
            parser ➡ symbol | list tree (SX)
                               ⬇
	symbol | list tree (SX) ⬅ preprocessor ⬅ rules-scopes.sx
	  ⬇
builder ➡ generic IR (NOIR + meta-instructions)
                        ⬇
	specific IR (NOIR) ⬅ reducer ⬅ rules-renoir.sx
	   ⬇           ⬇
	validator ➡ C target ➡ text (.c)
                                ⬇
      	object file (.o) ⬅ gcc
                   ⬇
	             ld ➡ binary file (.so, .out)
2024-10-23

Встречаем yx_scope: DI-фреймворк для работы со скоупами в открытом доступе

Для больших проектов не всегда хватает одного модуля: иногда надо пошарить какие‑нибудь классы или UI‑элементы. Так со временем проект дробится на много мелких модулей, которые так или иначе связаны разного рода зависимостями. И если за этим не следить, то рано или поздно структура проекта может стать запутанной. Наша команда разрабатывает приложение Яндекс Про, которым пользуются водители и курьеры. Из‑за многомодульности разные команды использовали разные подходы к связыванию зависимостей — в основном это getIt , injectable и riverpod . Но у всех решений были свои недостатки. К тому же то, что в одном проекте используется несколько подходов, сильно усложняло взаимодействие команд. Сложности подтолкнули нас к поиску собственного решения, которое удовлетворяло бы всем нашим требованиям. И теперь мы готовы поделиться им с комьюнити: наше решение — это группа библиотек yx_scope . Расскажу, зачем нужны скоупы и как они работают, в чём преимущества нашего фреймворка и как его использовать.

habr.com/ru/companies/yandex/a

#dart #flutter #di #dependency_injection #scopes

Allianz für Entwicklung&Klimaentwicklung_und_klima
2024-06-04

📅 Melden Sie sich jetzt noch an!
➡️ „Treibhausgas-Bilanzierung entlang der Lieferkette (Scope 3)."
in am 11.06.2024.

➡️ Anmeldung, Agenda und weitere Informationen: allianz-entwicklung-klima.de/t

2024-05-20
should i make a #vent #account or should i just learn about #privacy #scopes
2024-05-10

noticed on ubuntu 24.04 that libtinfo5 is no longer a package (you have to manually install a dpkg), but the LLVM 13 binary distro that we still use in scopes depends on it, so i took that as a sign that our dependency is rapidly getting very very old.

therefore, i finally ported our #scopes backend from LLVM 13 to LLVM 17, and even though they completely removed typed pointers, the port only ended up taking me 3 hours (but I felt *very* lost in the beginning).

2024-04-24

the f"..." string formatting prefix in #scopes

none of these do produce any intermediate string objects. it's all streamed.

i wonder how far i can drive this. like, could we fit an entire ascii flex layouter in there? ;-)

$9 ► f"test[0x{} {}]" (/hex 123) (f"<{}>" ~@i32)
$9 = test[0x7b <(mutable@ i32)>]
$10 ► /p (f"test[0x{} {}]" (/hex 123) (f"<{}>" ~@i32))
$10 = (test[0x7b <(mutable@ i32)>])
$11 ► /nostyle (/p (f"test[0x{} {}]" (/hex 123) (f"<{}>" ~@i32)))
$11 = (test[0x7b <(mutable@ i32)>])
2024-04-24

thinking about a short hand for the `mutable` qualifier in #scopes. the shortest synonym of mutable is "fluid", and "~" is an associated iconographic character. which readily makes this operation available:

$0 ► type+ type 
....     inline __~ (cls) 
....         mutable cls
....         
$0 = type
$1 ► ~i32
$1 = i32
$2 ► ~@i32
$2 = (mutable@ i32)
$3 ► ~&i32
$3 = (mutable& i32)
$4 ► ~rawstring
$4 = (mutable@ i8)
$5 ►
2024-04-13

some nice operations that can be performed on the exp2-heap i'm working on. efficiently base any pointer, find its size, offset it safely. the pointers require no extra tags and can be passed to C as-is. (in fact, when overriding the system malloc, all C libraries will produce these pointers)

as an important bonus, there's an extra bitmap segment that runs parallel to the pool at ratio 1:64 which is used to mark memory locations that are themselves addresses.

#scopes²

inline ptr-logcapacity (p)
    (p >> pool-size-bits) & pool-index-mask

inline ptr-capacity (p)
    1:usize << (ptr-logcapacity p)

inline ptr-base (p)
    p := ptrtoint p intptr
    cap := ptr-capacity p
    inttoptr (p & -cap) voidstar

# offset pointer by address or produce nullpointer
inline ptr-offset (p offset)
    offset := imply offset intptr
    p := ptrtoint p intptr
    cap := ptr-capacity p
    pos := p & (cap - 1)
    if ((pos + offset) >= cap)
        null as voidstar
    else
        inttoptr (p + offset) voidstar
2024-03-12

added three new features to #scopes core:
1. the parser recognizes and expands prefixed symbolic literals
2. the `c` string literal prefix now also supports symbols
3. the `c` prefix expands multi-character sequences up to 8 bytes (in LE) for easier definition of RIFF codes

$0 ► 'x
$0 = 'x
$1 ► c'x
$1 = 120:i8
$2 ► c'xy
$2 = 31096:u16
$3 ► c'xyzw
$3 = 2004515192:u32
$4 ►
2024-03-11

(i wrote this in our discord)
like rust, #scopes defines itself as a systems programming language, it just feels more entitled to unconstrained expression; systems programmers are far too ready to stunt their vocabulary and lock their jail cell from the inside, but then complain about feeling burned out later. i have been there in my 30s, and so i see that as flagrant disregard for one's needs. program performance is no altar at which to sacrifice your ability to concisely express your ideas.

2024-03-07

alright. i built a simple toy serializer for #scopes that just uses the existing print module to dump serialized values to the console.

already it can do many of the standard types, and even handle shared references.

but i will have to write a default binary serializer/deserializer next to know if the interface makes sense.

fn test1 ()
    using import Rc

    local a : (Rc (Array i32))

    Point := tuple (x = i32) (y = i32)

    local value = tupleof
        x = 303:u32
        y = 3.5
        z = copy a
        w = copy a
        arrayof Point (Point 1 2) (Point 3 4)
        q = tupleof 1 true 5 false

    'append a 1
    'append a 2
    'append a 3

    print
        /encode value
    ;{(x = 303)
    (y = 3.5)
    (z =
        {@1 =
            [1 2 3]})
    (w = @1)
    [{(x = 1)
            (y = 2)}
        {(x = 3)
            (y = 4)}]
    (q =
        {1 true 5 false})}
2024-03-05

rewrote the #scopes tokenizer in scopes as a collector. now it's possible to color-code scopes sources when streaming them from a file to the terminal.

2024-03-03
2024-02-19

i'm porting the TLSF allocator from C to #scopes. it's a pleasure, the code is very well written and documented.

2024-02-07

@kim_harding What definitions are being used - territorial, production, consumption? Journalists need #CarbonLiteracy #EmissionsOwnership #Scopes

Allianz für Entwicklung&Klimaentwicklung_und_klima
2024-02-02

💭 Was sind eigentlich ? Und welche Rolle spielen sie bei der Berechnung der unternehmensbezogenen Treibhausgasemissionen?

Unternehmen emittieren Treibhausgase. Nicht alle Emissionen sind aber auf den ersten Blick erkennbar. Um unternehmensbezogene THG-Emissionen zu berechnen, werden diese in drei Geltungsbereiche (=Scopes) geordnet und berechnet.

➡️ Mehr zu Scope 1, 2 und 3: allianz-entwicklung-klima.de/t
🔎 Zum Scopes-Factsheet: allianz-entwicklung-klima.de/w

2024-01-18

I have a recent LLM guess the language of snippets written in #scopes, and it thinks it's a dialect of Rust. that's not too far away, actually.

Client Info

Server: https://mastodon.social
Version: 2025.04
Repository: https://github.com/cyevgeniy/lmst