doge-compiler 0.3.2

Compiler for the Doge programming language — lexer, parser, semantic checks, and Rust codegen.
Documentation 
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155

use super::*;

pub(super) fn diag(path: &str, source: &str, span: Span, message: impl Into<String>) -> Diagnostic {
    let lines = crate::diagnostics::split_source_lines(source);
    Diagnostic::new(
        path,
        span.line,
        span.col,
        crate::diagnostics::source_line(&lines, span.line),
        message,
    )
}

/// The "doge has no module named X" diagnostic for the stdlib-only path (used by
/// `single_file_program`), nudging `math` toward `nerd`.
pub(crate) fn unknown_stdlib_module(
    path: &str,
    source: &str,
    name: &str,
    span: Span,
) -> Diagnostic {
    let hint = if name == "math" {
        "much math? such nerd — write so nerd".to_string()
    } else {
        format!("modules: {}", stdlib::module_names())
    };
    diag(
        path,
        source,
        span,
        format!("doge has no module named {name}"),
    )
    .with_headline("very import. much unknown.")
    .with_hint(hint)
}

/// The "no such module, and no file for it either" diagnostic for a user import
/// whose `<name>.doge` is not next to the importing file.
pub(super) fn missing_module_diag(path: &str, source: &str, name: &str, span: Span) -> Diagnostic {
    let hint = if name == "math" {
        "much math? such nerd — write so nerd".to_string()
    } else {
        format!(
            "make {name}.doge next to this file, or import a stdlib module ({})",
            stdlib::module_names()
        )
    };
    diag(
        path,
        source,
        span,
        format!("doge has no module named {name}"),
    )
    .with_headline("very import. much unknown.")
    .with_hint(hint)
}

/// The "no file at this path" diagnostic for a string-path import whose target
/// is not on disk, relative to the importing file.
pub(super) fn missing_path_module_diag(
    path: &str,
    source: &str,
    raw: &str,
    target: &Path,
    span: Span,
) -> Diagnostic {
    diag(path, source, span, format!("doge found no file at {raw}"))
        .with_headline("very import. much unknown.")
        .with_hint(format!(
            "paths are relative to this file — doge looked at {}",
            target.display()
        ))
}

/// A module (or the entry itself) importing the entry script back: the entry is
/// not a module — it holds loose top-level statements that run, so it can never
/// be imported.
pub(super) fn entry_import_diag(path: &str, source: &str, span: Span) -> Diagnostic {
    diag(
        path,
        source,
        span,
        "this import points back at the main script, which is not a module",
    )
    .with_headline("very import. much self.")
    .with_hint("only modules (definitions-only files) can be imported — split the shared code into its own file")
}

pub(super) fn read_error_diag(
    path: &str,
    source: &str,
    name: &str,
    target: &Path,
    err: &std::io::Error,
    span: Span,
) -> Diagnostic {
    diag(
        path,
        source,
        span,
        format!("doge found {name}.doge but could not read it: {err}"),
    )
    .with_headline("very import. much unreadable.")
    .with_hint(format!("check the file at {}", target.display()))
}

/// A user file whose name collides with a stdlib module: the import would always
/// mean the stdlib, so the file can never be reached — a name to fix now.
pub(super) fn shadow_diag(path: &str, source: &str, name: &str, span: Span) -> Diagnostic {
    diag(
        path,
        source,
        span,
        format!("{name}.doge shadows the built-in module {name}"),
    )
    .with_headline("very shadow. much confuse.")
    .with_hint(format!("rename your file — {name} is a doge stdlib module"))
}

/// A name that is both a declared dependency and a sibling `<name>.doge`: the
/// import can't mean both, so the ambiguity must be resolved by renaming one.
pub(super) fn dep_conflict_diag(path: &str, source: &str, name: &str, span: Span) -> Diagnostic {
    diag(
        path,
        source,
        span,
        format!("{name} is both a declared dependency and a file {name}.doge here"),
    )
    .with_headline("very ambiguous. much confuse.")
    .with_hint(format!(
        "rename one — a dependency and a sibling module can't share the name {name}"
    ))
}

/// A circular import: `active` is the chain of modules currently being loaded,
/// and `name` closes the loop back onto one of them.
pub(super) fn cycle_diag(
    path: &str,
    source: &str,
    active: &[String],
    name: &str,
    span: Span,
) -> Diagnostic {
    let start = active.iter().position(|m| m == name).unwrap_or(0);
    let mut chain: Vec<&str> = active[start..].iter().map(String::as_str).collect();
    chain.push(name);
    diag(
        path,
        source,
        span,
        format!("import cycle: {}", chain.join(" → ")),
    )
    .with_headline("very loop. much import.")
    .with_hint("break the loop — one of these imports has to go")
}