1 May 2026, 11:57 UTC25 viewsread 13 August 2026
github с исходным кодом: https://github.com/Freyzan2006/step-compiler-code-example
![Telegram profile photo for Freyzan[ IT ]](https://cdn.tgregister.com/av/b6/b6c3d509ccc2c1233fb076977b5038cf02f2533f2db41c88cac4240b0ce6b063.jpg)
Channel
Freyzan[ IT ]
@freyzanIT
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
4subscribers
+0 since we began measuring on 10 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
Register entry
| Telegram ID | -1002709926296 |
|---|---|
| Type | Channel |
| Username | @freyzanIT |
| Created | 9 July 2025 — measured — dated from the channel’s first post |
| First recorded | 13 August 2026 |
| Last confirmed live | 1 September 2026 |
| Measurements held | 2 |
| On Telegram | t.me/freyzanIT |
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 13 Aug 2026, 09:48 | 4 | no change |
| 10 Aug 2026, 03:45 | 4 | first reading |
Engagement
19 posts held, back to 9 July 2025 — the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 1 page of Telegram’s post history, 20 posts per page.
Nothing published in the last 30 days. ERR and ER are rolling 30-day measures, so there is nothing to compute — we hold 19 posts for this entry, the most recent from 1 May 2026. An engagement rate over an empty window would be a number about nothing.
What this channel posts
- Photos
- 8
- Links
- 5
Lifetime counters from Telegram’s own channel header, read 13 August 2026 — not the date at the top of this page, which is when the subscriber count was last read. Below Telegram’s rounding threshold, so these counts are exact.
Reaction mix
6 reactions across 2 posts, in 4 distinct kinds. The most used accounts for 33.3% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 👍 | 2 | 33.3% | |
| 🔥 | 2 | 33.3% | |
| ❤ | 1 | 16.7% | |
| 👌 | 1 | 16.7% |
No sentiment is inferred, and none should be read in. This table is ordered by count and by nothing else. Emoji do not carry stable meaning across languages or communities — 🙏 is thanks in one channel and mourning in another — so we publish which ones were pressed and how often, and pass no judgement on what an audience meant by them.
Precision. Telegram publishes reaction counts per emoji and short-forms each one — 4.34K, 1.2M — so any single kind at or above 1,000 reaches us at three significant figures, and only counts below 1,000 are exact. The shares above are ratios of those figures and carry the same error. This is also why the total here can differ slightly from a reaction total printed elsewhere on the page: both are sums of the same rounded parts, taken over samples with different edges.
Coverage. Reactions were read on 2 of the 19 sampled posts in this sample. Summed by Telegram’s own count on each post — not by adding up the per-emoji breakdown above — those same posts carry 6 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 19 most recent posts we hold, published 9 July 2025 to 1 May 2026, using the newest reading held for each. Telegram Stars are excluded: they are a payment, not a reaction, and they have their own section.
Recent posts
1 May 2026, 11:38 UTC14 viewsread 13 August 2026
Forwarded from @fullStackDevelopment55
Origin IR: IRInstruction(op='LOAD_CONST', arg1=3, arg2=None, result='t1') IRInstruction(op='STORE', arg1='t1', arg2=None, result='b') IRInstruction(op='LOAD_CONST', arg1=10, arg2=None, result='t2') IRInstruction(op='ADD', arg1='t2', arg2='b', result='t3') IRInstruction(op='STORE', arg1='t3', arg2=None, result='a') IRInstruction(op='LOAD_CONST', arg1=2, arg2=None, result='t4') IRInstruction(op='MUL', arg1='a', arg2='t…
1 May 2026, 11:38 UTC9 viewsread 13 August 2026
Forwarded from @fullStackDevelopment55
1. Constant Folding тут мы заранее оптимизируем константы и их вычисления до код: int a = 2 * 3 до IR IRInstruction(op='LOAD_CONST', arg1=3, arg2=None, result='t1') IRInstruction(op='LOAD_CONST', arg1=2, arg2=None, result='t4') IRInstruction(op='MUL', arg1='t1', arg2='t2', result='t3') После код: int a = 6 После IR IRInstruction(op='LOAD_CONST', arg1=6, arg2=None, result='t1') 2. Constant Propagation Если переме…
1 May 2026, 11:38 UTC8 viewsread 13 August 2026
Forwarded from @fullStackDevelopment55Photo
Следующий этап "Оптимизация". Оптимизации (Compile-time optimizations) - это процесс когда мы, улучшаем скорость работы программы, на уровне компиляции, при этом сохраняем правельность работы программы. Это преобразования программы, которые: * выполняются во время компиляции * не меняют результат программы * улучшают производительность / размер / читаемость IR Мы проведём самые базовые 3 вида оптимизаций в нашем …
1 May 2026, 11:38 UTC8 viewsread 13 August 2026
Forwarded from @fullStackDevelopment55Photo
После проверки программы на осмысленные конструкции, идёт следующий этап Intermediate Representation (IR) - данный слой решает проблему, связанную с тем что AST является удобным для анализа Напомню AST: [VarDeclaration(var_type='int', name='b', value=Number(value=3)), VarDeclaration(var_type='int', name='a', value=BinaryOp(left=Number(value=10), operator='+', right=Identifier(name='b'))), VarDeclaration(var_type='i…
1 May 2026, 11:38 UTC6 viewsread 13 August 2026
Forwarded from @fullStackDevelopment55Photo
После проверки структуры кода и создания AST идёт этап Семантического анализа(Semantic Analyzer) Semantic Analyzer - это процесс когда код программы, проверяется на осмысленность программы, к примеру: ———— Код: int a = b + 10; Ошибка Variable 'b' not defined ———— Код: int a = 10; int a = 20; Ошибка Variable 'a' already declared ———— и еще довольно большой раяд подобных проверок. На выходе данного layer мы получ…
1 May 2026, 11:38 UTC6 viewsread 13 August 2026
Forwarded from @fullStackDevelopment55Photo
Синтаксический анализ (Parsing) - исходня из названию, данный слой получает на вход набор токенов, которые мы получили с слоя lexer и на выходе получаем AST. Parsing: - корректен ли порядок токенов - соблюдены ли правила языка - можно ли из этого построить осмысленную конструкцию Данный слой позволяет нам связать token в структуру под названием AST AST(Абстрактное сентаксическое дерево) - это структура данных, поз…
1 May 2026, 11:38 UTC7 viewsread 13 August 2026
Forwarded from @fullStackDevelopment55Photo
Лексический анализ — это первый этап компиляции. На этом этапе исходный код разбивается на последовательность токенов. Лексер читает поток символов, группирует их в лексемы и классифицирует согласно правилам языка. Пробелы, табуляции, переносы строк и комментарии обычно игнорируются. Результатом работы является поток токенов, который передаётся на этап синтаксического анализа. Пример: int a = 10 + b выходит: KEYWORD…
1 May 2026, 11:38 UTC8 viewsread 13 August 2026
Forwarded from @fullStackDevelopment55Photo
Любой написанный код является просто набором байтов в памяти, но с компилятором наш код обретает логическую интерпретацию. Данное превращение из набора символов в набор команд делится на 8 этапов: 1. Лексический анализ (Lexical analysis) 2. Синтаксический анализ (Parsing) 3. Семантический анализ 4. Построение промежуточного представления (IR) 5. Оптимизации (Compile-time optimizations) 6. Генерация кода 7. Лин…
1 May 2026, 11:38 UTC7 viewsread 13 August 2026
Forwarded from @fullStackDevelopment55Photo
Работа языко программирования №1 Многие из вас, сейчас читающих данный пост, умеют писать код на разных языках. Но немногие понимают и знают работу этих языков, то, как они реализованы, и то, что происходит, когда вы запускаете свой код. Данный пост открывает арку постов, связанных с этой темой; все последующие посты — 3–4 шт.
1 May 2026, 11:38 UTC13 views3 reactionsread 13 August 2026
Forwarded from @fullStackDevelopment55Photo
Этап Code Generation - самый интересный этап, давайте освежим в памяти весь pipline: 0. Source code 1. Lexer 2. Parser 3. AST 4. Semantic Analysis 5. IR 6. Optimization 7. Code Generation * Есть несколько вариантов генерации: - Assembly (x86-64) - Bytecode (как у JVM) - WebAssembly - Интерпретация IR Мы возьмём вариант Интерпретация IR. IR Interpreter: выполняет инструкции по типу таких IRInstruction(op='STORE', a…
👌1👍1🔥1
1 May 2026, 11:38 UTC9 views3 reactionsread 13 August 2026
Forwarded from @fullStackDevelopment55
Реализация в коде: Интепритатор(core.intepritator.py): from typing import Dict class IRInterpreter: def __init__(self): self.variables: Dict = {} self.temps: Dict = {} def get_value(self, name): if isinstance(name, (int, float)): return name if name in self.temps: return self.temps[name] if name in self.variables: return self.v…
❤1👍1🔥1
Showing the 12 most recent of 19 posts we hold for @freyzanIT. View and reaction counts are the latest single reading for each post, not a live figure, and a recent post is still accumulating both. A view count marked ≈ was rounded by Telegram before we ever saw it — t.me prints views in full below 1,000 and to three significant figures above, so ≈1,200,000 means somewhere between 1,150,000 and 1,249,999. Unmarked counts are exact. Text is reproduced from the public post preview and truncated for length.
Forward network
Republishes
Channels on the register whose posts this channel has forwarded.
Built only from forwarded posts we have actually read, on both sides. Coverage is early and deliberately incomplete: a missing link means we have not read the post that would prove it, never that the relationship does not exist. Counts are distinct forwarded posts observed, so they only ever go up as we read more.
Mentions
Named by 1 registered channel — every channel on the register whose own posts have named this one, by its current username or any other username it currently holds, merged from two separately captured readings of the same fact so a namer caught by only one of them is not missed and a namer both caught is not counted twice. A username this channel has since dropped is not matched — that handle may belong to someone else now, and crediting today’s namer to yesterday’s owner would misattribute it.
Named by
Channels on the register whose posts name this channel's handle.
A mention is a weaker signal than a forward and is counted separately for that reason — naming a channel is not republishing it, and a handle in a post body is easy to place deliberately. The post counts beside each row below are distinct posts in which the handle appeared, from posts we have read on both sides — the “Named by N registered channels” figure above is a different count, of distinct NAMING CHANNELS rather than posts, and is not the sum of the rows under it.
Cite this entry
A live page changes as we take new readings, so a citation should name the measurement it is based on, not just the URL. The line below cites the subscriber count as measured 13 August 2026 — this entry's latest reading, not the date you are reading this.
“Freyzan[ IT ]” (@freyzanIT), 4 subscribers as measured 13 August 2026. Telegram Register, tgregister.com/channel/freyzanIT.
Full measurement history, CC BY 4.0. Every reading this register holds for this entry, not just the latest one, as a dated, downloadable record: CSV · JSON. Free to use with attribution to tgregister.com. Each file carries its own generation timestamp, which is the figure to cite for exactly when the data was retrieved.