* [PATCH olang 0/4] comment based integration tests
@ 2024-05-12 14:30 Carlos Maniero
2024-05-12 14:30 ` [PATCH olang 1/4] tests: add comment based integration tests mechanism Carlos Maniero
` (5 more replies)
0 siblings, 6 replies; 83+ messages in thread
From: Carlos Maniero @ 2024-05-12 14:30 UTC (permalink / raw)
To: ~johnnyrichard/olang-devel; +Cc: Carlos Maniero
The old munit based integration tests was replaced by a new mechanism
that makes testing more tasteful and easy to perform.
To create an integration tests you just need to create a olang file at
*tests/integration/tests* directory. The assertions are performed
thought a couple of comments.
# spec: some text to describe what are you testing
# compiler_exit: the compilers exit code
# compiler_output: the compilers output, %empty% for empty output
# program_exit: the program exit code
# ast: the ast output
# tokens: the tokens
This patchset also includes parser tests errors and creates a TODO
mechanism that can be used to track what need to be implemented.
Carlos Maniero (4):
tests: add comment based integration tests mechanism
tests: remove previous integration tests structure
tests: include integration tests for function parser errors
tests: print integration tests TODOs
Makefile | 1 -
tests/integration/Makefile | 33 +--
tests/integration/cli_runner.c | 100 ---------
tests/integration/cli_runner.h | 32 ---
tests/integration/cli_test.c | 132 ------------
tests/integration/proc_exec.c | 63 ------
tests/integration/proc_exec.h | 37 ----
tests/integration/test.sh | 195 ++++++++++++++++++
tests/integration/tests/0001_main_exit.ol | 27 +++
.../tests/0002_fn_without_fn_keyword.ol | 8 +
.../integration/tests/0003_fn_without_type.ol | 8 +
.../tests/0004_fn_without_type_colon.ol | 8 +
.../0005_fn_without_open_curly_brackets.ol | 8 +
.../0006_fn_without_close_curly_brackets.ol | 7 +
.../tests/0007_fn_without_return.ol | 8 +
15 files changed, 277 insertions(+), 390 deletions(-)
delete mode 100644 tests/integration/cli_runner.c
delete mode 100644 tests/integration/cli_runner.h
delete mode 100644 tests/integration/cli_test.c
delete mode 100644 tests/integration/proc_exec.c
delete mode 100644 tests/integration/proc_exec.h
create mode 100755 tests/integration/test.sh
create mode 100644 tests/integration/tests/0001_main_exit.ol
create mode 100644 tests/integration/tests/0002_fn_without_fn_keyword.ol
create mode 100644 tests/integration/tests/0003_fn_without_type.ol
create mode 100644 tests/integration/tests/0004_fn_without_type_colon.ol
create mode 100644 tests/integration/tests/0005_fn_without_open_curly_brackets.ol
create mode 100644 tests/integration/tests/0006_fn_without_close_curly_brackets.ol
create mode 100644 tests/integration/tests/0007_fn_without_return.ol
--
2.34.1
^ permalink raw reply [flat|nested] 83+ messages in thread
* [PATCH olang 1/4] tests: add comment based integration tests mechanism
2024-05-12 14:30 [PATCH olang 0/4] comment based integration tests Carlos Maniero
@ 2024-05-12 14:30 ` Carlos Maniero
2024-05-12 14:30 ` [PATCH olang 2/4] tests: remove previous integration tests structure Carlos Maniero
` (4 subsequent siblings)
5 siblings, 0 replies; 83+ messages in thread
From: Carlos Maniero @ 2024-05-12 14:30 UTC (permalink / raw)
To: ~johnnyrichard/olang-devel; +Cc: Carlos Maniero
The old munit based integration tests was replaced by a new mechanism
that makes testing more tasteful and easy to perform.
To create an integration tests you just need to create a olang file at
*tests/integration/tests* directory. The assertions are performed
thought a couple of comments.
spec: some text to describe what are you testing
compiler_exit: the compilers exit code
compiler_output: the compilers output, %empty% for empty output
program_exit: the program exit code
ast: the ast output
tokens: the tokens
Since the language has the line_feed token it is impossible to test the
EOF once when added a comment the EOF will be located at line + 1. So
that the tokens test the first n-lines defined. The AST compares the
entire AST tough.
Signed-off-by: Carlos Maniero <carlos@maniero.me>
---
Makefile | 1 -
tests/integration/Makefile | 33 +---
tests/integration/test.sh | 182 ++++++++++++++++++++++
tests/integration/tests/0001_main_exit.ol | 27 ++++
4 files changed, 217 insertions(+), 26 deletions(-)
create mode 100755 tests/integration/test.sh
create mode 100644 tests/integration/tests/0001_main_exit.ol
diff --git a/Makefile b/Makefile
index cdfc8e1..a0130f5 100644
--- a/Makefile
+++ b/Makefile
@@ -19,7 +19,6 @@ $(BUILD_DIR):
.PHONY: linter
linter: $(SRCS) $(HEADERS)
clang-format --dry-run --Werror $?
- $(MAKE) -C tests/integration/ linter
$(MAKE) -C tests/unit/ linter
.PHONY: linter-fix
diff --git a/tests/integration/Makefile b/tests/integration/Makefile
index db2b7d9..567ce88 100644
--- a/tests/integration/Makefile
+++ b/tests/integration/Makefile
@@ -1,31 +1,14 @@
-SRCS := $(wildcard *_test.c)
-OBJS := $(patsubst %_test.c, %_test.o, $(SRCS))
-CFLAGS := -I../../src -I../shared
-TESTS := $(patsubst %_test.c, %_test, $(SRCS))
-EXEC_TESTS := $(patsubst %_test, ./%_test, $(TESTS))
-MUNIT_SRC := ../shared/munit.c
-MUNIT := ./munit.o
+TESTER_SRC := ./test.sh
+TESTS := $(wildcard ./tests/*.ol)
.PHONY: all
-all: $(MUNIT) proc_exec.o cli_runner.o $(TESTS)
- @for file in $(EXEC_TESTS); do \
- ./"$$file"; \
+all:
+ @set -e; \
+ for file in $(TESTS); do \
+ $(TESTER_SRC) "$$file"; \
+ echo; \
done
.PHONY: clean
clean:
- $(RM) *.o *_test
-
-.PHONY: linter
-linter: $(SRCS)
- clang-format --dry-run --Werror $?
-
-.PHONY: linter-fix
-linter-fix: $(SRCS)
- clang-format -i $?
-
-cli_test: $(MUNIT) proc_exec.o cli_runner.o cli_test.o
- $(CC) $? $(CFLAGS) -o $@
-
-$(MUNIT):
- $(CC) -c $(MUNIT_SRC) $(CFLAGS) -o $(MUNIT)
+ @rm -rf ./tests/*.ol.test*
diff --git a/tests/integration/test.sh b/tests/integration/test.sh
new file mode 100755
index 0000000..6ab03de
--- /dev/null
+++ b/tests/integration/test.sh
@@ -0,0 +1,182 @@
+COMPILER_PATH="../../olang"
+TEST_FILE="$1"
+
+PROGRAM="$TEST_FILE.test"
+
+COMPILER_OUTPUT_FILE="$TEST_FILE.test.compiler_output"
+COMPILER_EXPECT_OUTPUT_FILE="$TEST_FILE.test.expected_compiler_output"
+
+AST_OUTPUT_FILE="$TEST_FILE.test.ast_output"
+AST_EXPECT_OUTPUT_FILE="$TEST_FILE.test.expected_ast_output"
+
+TOKENS_OUTPUT_FILE="$TEST_FILE.test.tokens_output"
+TOKENS_EXPECT_OUTPUT_FILE="$TEST_FILE.test.expected_tokens_output"
+
+TOKENS_OUTPUT_FILE="$TEST_FILE.test.tokens_output"
+TOKENS_EXPECT_OUTPUT_FILE="$TEST_FILE.test.expected_tokens_output"
+
+PROGRAM_OUTPUT="$TEST_FILE.test.program_output"
+
+extract_comment() {
+ tag="$1"
+ comment="# $tag: "
+ cat $TEST_FILE | grep "$comment" | sed -e "s/$comment//"
+}
+
+# UI
+COLOR_RED=1
+COLOR_GREEN=2
+COLOR_YELLOW=3
+COLOR_BLUE=4
+COLOR_CYAN=6
+COLOR_GRAY=7
+
+colored() {
+ text="$1"
+ color="$2"
+ if [ -t 1 ]; then
+ if tput setaf 1 &> /dev/null; then
+ printf "$(tput setaf $color)$text$(tput sgr0)"
+ return
+ fi
+ fi
+
+ printf "$text"
+}
+
+print_test_description() {
+ colored "$TEST_FILE: \n" $COLOR_CYAN
+ colored "$(extract_comment spec)\n\n" $COLOR_GRAY
+}
+
+print_passed() {
+ context="$1"
+ printf "$context: "
+ colored "passed" $COLOR_GREEN
+ echo
+}
+
+print_failed() {
+ context="$1"
+ printf "$context: "
+ colored "failed" $COLOR_RED
+ echo
+}
+
+print_skiped() {
+ context="$1"
+ printf "$context: "
+ colored "not set" $COLOR_GRAY
+ echo
+}
+
+# Assertions
+expect_exit_code() {
+ context="$1"
+ expected="$2"
+ actual="$3"
+
+ if [ -z "$expected" ]; then
+ print_skiped "$context"
+ echo "no expected exit code set, it exited with \"$actual\"."
+ else
+ if [ "$expected" = "$actual" ]; then
+ print_passed "$context"
+ else
+ print_failed "$context"
+ colored "Expected exit code: " $COLOR_YELLOW
+ colored "$expected" $COLOR_GRAY
+ colored ", actual: " $COLOR_YELLOW
+ colored "$actual\n" $COLOR_GRAY
+ exit 1
+ fi
+ fi
+}
+
+expect_output() {
+ context="$1"
+ expected_file="$2"
+ actual_file="$3"
+
+ if [ "$(cat $expected_file | wc -l)" = "0" ]; then
+ print_skiped "$context"
+ return
+ fi
+
+ if cmp -s "$expected_file" "$actual_file"; then
+ print_passed "$context"
+ else
+ if [ "$(cat "$expected_file")" = "%empty%" ]; then
+ if [ "$(cat $actual_file | wc -c)" = "0" ]; then
+ print_passed "$context"
+ return
+ fi
+ fi
+ print_failed "$context"
+ colored "$context not match:\n" $COLOR_YELLOW
+ diff "$actual_file" "$expected_file" -u --color
+ exit 1
+ fi
+}
+
+cleanup() {
+ rm -f $PROGRAM*
+}
+
+test_compiler() {
+ $COMPILER_PATH $TEST_FILE -o $PROGRAM > "$COMPILER_OUTPUT_FILE" 2>&1
+
+ EXIT=$?
+ EXPECTED_EXIT=$(extract_comment compiler_exit)
+
+ expect_exit_code compiler_exit "$EXPECTED_EXIT" "$EXIT"
+
+ extract_comment compiler_output > $COMPILER_EXPECT_OUTPUT_FILE
+ expect_output compiler_output "$COMPILER_EXPECT_OUTPUT_FILE" "$COMPILER_OUTPUT_FILE"
+
+ if [ "$EXIT" = "1" ]; then
+ echo "program execution skiped since the compiler failed as expected."
+ cleanup
+ exit 0
+ fi
+}
+
+test_ast() {
+ $COMPILER_PATH $TEST_FILE --dump-ast > "$AST_OUTPUT_FILE" 2>&1
+
+ extract_comment ast > $AST_EXPECT_OUTPUT_FILE
+ expect_output "ast" "$AST_EXPECT_OUTPUT_FILE" "$AST_OUTPUT_FILE"
+}
+
+test_tokens() {
+ extract_comment tokens > $TOKENS_EXPECT_OUTPUT_FILE
+ TOKEN_LINES=$(cat $TOKENS_EXPECT_OUTPUT_FILE | wc -l)
+
+ $COMPILER_PATH $TEST_FILE --dump-tokens | head -n $TOKEN_LINES > "$TOKENS_OUTPUT_FILE" 2>&1
+
+ expect_output tokens $TOKENS_OUTPUT_FILE $TOKENS_EXPECT_OUTPUT_FILE
+
+ print_passed tokens
+}
+
+test_program() {
+ ./$PROGRAM
+
+ EXIT=$?
+ EXPECTED_EXIT=$(extract_comment program_exit)
+ expect_exit_code "program_exit" "$EXPECTED_EXIT" "$EXIT"
+}
+
+
+main() {
+ print_test_description
+
+ test_compiler
+ test_program
+ test_tokens
+ test_ast
+
+ cleanup
+}
+
+main
diff --git a/tests/integration/tests/0001_main_exit.ol b/tests/integration/tests/0001_main_exit.ol
new file mode 100644
index 0000000..c30492f
--- /dev/null
+++ b/tests/integration/tests/0001_main_exit.ol
@@ -0,0 +1,27 @@
+# spec: A minimal olang program
+fn main(): u32 {
+ return 0
+}
+# compiler_exit: 0
+# compiler_output: %empty%
+# program_exit: 0
+#
+# ast: Translation_Unit
+# ast: `-Function_Definition <name:main> <return:0>
+# ast: `-Block
+# ast: `-Return_Statement
+# ast: `-Literal <kind:u32> <value:0>
+#
+# tokens: ./tests/0001_main_exit.ol:1:32: <line_feed>
+# tokens: ./tests/0001_main_exit.ol:2:1: <fn>
+# tokens: ./tests/0001_main_exit.ol:2:4: <identifier>
+# tokens: ./tests/0001_main_exit.ol:2:8: <(>
+# tokens: ./tests/0001_main_exit.ol:2:9: <)>
+# tokens: ./tests/0001_main_exit.ol:2:10: <:>
+# tokens: ./tests/0001_main_exit.ol:2:12: <identifier>
+# tokens: ./tests/0001_main_exit.ol:2:16: <{>
+# tokens: ./tests/0001_main_exit.ol:2:17: <line_feed>
+# tokens: ./tests/0001_main_exit.ol:3:3: <return>
+# tokens: ./tests/0001_main_exit.ol:3:10: <number>
+# tokens: ./tests/0001_main_exit.ol:3:11: <line_feed>
+# tokens: ./tests/0001_main_exit.ol:4:1: <}>
--
2.34.1
^ permalink raw reply [flat|nested] 83+ messages in thread
* [PATCH olang 2/4] tests: remove previous integration tests structure
2024-05-12 14:30 [PATCH olang 0/4] comment based integration tests Carlos Maniero
2024-05-12 14:30 ` [PATCH olang 1/4] tests: add comment based integration tests mechanism Carlos Maniero
@ 2024-05-12 14:30 ` Carlos Maniero
2024-05-12 14:30 ` [PATCH olang 3/4] tests: include integration tests for function parser errors Carlos Maniero
` (3 subsequent siblings)
5 siblings, 0 replies; 83+ messages in thread
From: Carlos Maniero @ 2024-05-12 14:30 UTC (permalink / raw)
To: ~johnnyrichard/olang-devel; +Cc: Carlos Maniero
Signed-off-by: Carlos Maniero <carlos@maniero.me>
---
tests/integration/cli_runner.c | 100 -------------------------
tests/integration/cli_runner.h | 32 --------
tests/integration/cli_test.c | 132 ---------------------------------
tests/integration/proc_exec.c | 63 ----------------
tests/integration/proc_exec.h | 37 ---------
tests/integration/test.sh | 62 ++++++++--------
6 files changed, 33 insertions(+), 393 deletions(-)
delete mode 100644 tests/integration/cli_runner.c
delete mode 100644 tests/integration/cli_runner.h
delete mode 100644 tests/integration/cli_test.c
delete mode 100644 tests/integration/proc_exec.c
delete mode 100644 tests/integration/proc_exec.h
diff --git a/tests/integration/cli_runner.c b/tests/integration/cli_runner.c
deleted file mode 100644
index 636abfc..0000000
--- a/tests/integration/cli_runner.c
+++ /dev/null
@@ -1,100 +0,0 @@
-/*
- * Copyright (C) 2024 olang maintainers
- *
- * This program is free software: you can redistribute it and/or modify
- * it under the terms of the GNU General Public License as published by
- * the Free Software Foundation, either version 3 of the License, or
- * (at your option) any later version.
- *
- * This program is distributed in the hope that it will be useful,
- * but WITHOUT ANY WARRANTY; without even the implied warranty of
- * MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
- * GNU General Public License for more details.
- *
- * You should have received a copy of the GNU General Public License
- * along with this program. If not, see <https://www.gnu.org/licenses/>.
- */
-#include "cli_runner.h"
-#include "proc_exec.h"
-#include <assert.h>
-#include <stdbool.h>
-#include <stdio.h>
-#include <stdlib.h>
-#include <string.h>
-#include <sys/wait.h>
-#include <unistd.h>
-
-#define OLANG_COMPILER_PATH "../../olang"
-
-static int compiler_exists_already_checked = 0;
-
-static void
-assert_compiler_exists()
-{
- {
- if (compiler_exists_already_checked == 1) {
- return;
- }
-
- compiler_exists_already_checked = 1;
- }
-
- FILE *file = fopen(OLANG_COMPILER_PATH, "r");
-
- if (file != NULL) {
- fclose(file);
- return;
- }
-
- perror("Build the compiler before executing tests");
- exit(1);
-}
-
-void
-create_tmp_file_name(char *file_name)
-{
- sprintf(file_name, "%s/olang_programXXXXXX", P_tmpdir);
- int fd = mkstemp(file_name);
-
- if (fd == -1) {
- perror("Could not create a tmp file. Check your P_tmpdir permission.");
- exit(1);
- }
- close(fd);
-}
-
-void
-cli_runner_compiler(cli_result_t* result, char *args[])
-{
- assert_compiler_exists();
-
- proc_exec_command_t command = {
- .path = OLANG_COMPILER_PATH,
- .args = args
- };
-
- proc_exec(&command);
-
- result->exec = command.result;
-}
-
-cli_result_t
-cli_runner_compiler_dump_tokens(char *src)
-{
- cli_result_t result = { 0 };
-
- char *program_args[] = { "olang", "--dump-tokens", src, NULL };
- cli_runner_compiler(&result, program_args);
- return result;
-}
-
-cli_result_t
-cli_runner_compiler_compile(char *src)
-{
- cli_result_t result = { 0 };
- create_tmp_file_name(result.binary_path);
-
- char *program_args[] = { "olang", src, "-o", result.binary_path, NULL };
- cli_runner_compiler(&result, program_args);
- return result;
-}
diff --git a/tests/integration/cli_runner.h b/tests/integration/cli_runner.h
deleted file mode 100644
index 785cd34..0000000
--- a/tests/integration/cli_runner.h
+++ /dev/null
@@ -1,32 +0,0 @@
-/*
- * Copyright (C) 2024 olang maintainers
- *
- * This program is free software: you can redistribute it and/or modify
- * it under the terms of the GNU General Public License as published by
- * the Free Software Foundation, either version 3 of the License, or
- * (at your option) any later version.
- *
- * This program is distributed in the hope that it will be useful,
- * but WITHOUT ANY WARRANTY; without even the implied warranty of
- * MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
- * GNU General Public License for more details.
- *
- * You should have received a copy of the GNU General Public License
- * along with this program. If not, see <https://www.gnu.org/licenses/>.
- */
-#ifndef CLI_RUNNER_H
-#define CLI_RUNNER_H
-#include "proc_exec.h"
-
-typedef struct cli_result_t
-{
- char binary_path[255];
- proc_exec_result_t exec;
-} cli_result_t;
-
-cli_result_t
-cli_runner_compiler_dump_tokens(char *src);
-
-cli_result_t
-cli_runner_compiler_compile(char *src);
-#endif
diff --git a/tests/integration/cli_test.c b/tests/integration/cli_test.c
deleted file mode 100644
index e7ae059..0000000
--- a/tests/integration/cli_test.c
+++ /dev/null
@@ -1,132 +0,0 @@
-/*
- * Copyright (C) 2024 olang maintainers
- *
- * This program is free software: you can redistribute it and/or modify
- * it under the terms of the GNU General Public License as published by
- * the Free Software Foundation, either version 3 of the License, or
- * (at your option) any later version.
- *
- * This program is distributed in the hope that it will be useful,
- * but WITHOUT ANY WARRANTY; without even the implied warranty of
- * MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
- * GNU General Public License for more details.
- *
- * You should have received a copy of the GNU General Public License
- * along with this program. If not, see <https://www.gnu.org/licenses/>.
- */
-#define MUNIT_ENABLE_ASSERT_ALIASES
-#include "cli_runner.h"
-#include "munit.h"
-#include <stdio.h>
-
-static MunitResult
-test_cli_dump_tokens_example_main_exit(const MunitParameter params[], void *user_data_or_fixture)
-{
- cli_result_t compilation_result = cli_runner_compiler_dump_tokens("../../examples/main_exit.ol");
- munit_assert_int(compilation_result.exec.exit_code, ==, 0);
- munit_assert_string_equal(compilation_result.exec.stdout_buf,
- "../../examples/main_exit.ol:1:12: <line_feed>\n"
- "../../examples/main_exit.ol:2:16: <line_feed>\n"
- "../../examples/main_exit.ol:3:1: <line_feed>\n"
- "../../examples/main_exit.ol:4:1: <fn>\n"
- "../../examples/main_exit.ol:4:4: <identifier>\n"
- "../../examples/main_exit.ol:4:8: <(>\n"
- "../../examples/main_exit.ol:4:9: <)>\n"
- "../../examples/main_exit.ol:4:10: <:>\n"
- "../../examples/main_exit.ol:4:12: <identifier>\n"
- "../../examples/main_exit.ol:4:16: <{>\n"
- "../../examples/main_exit.ol:4:17: <line_feed>\n"
- "../../examples/main_exit.ol:5:3: <return>\n"
- "../../examples/main_exit.ol:5:10: <number>\n"
- "../../examples/main_exit.ol:5:11: <line_feed>\n"
- "../../examples/main_exit.ol:6:1: <}>\n"
- "../../examples/main_exit.ol:6:2: <line_feed>\n"
- "../../examples/main_exit.ol:7:1: <EOF>\n");
- return MUNIT_OK;
-}
-
-static MunitResult
-test_cli_dump_tokens_example_expression(const MunitParameter params[], void *user_data_or_fixture)
-{
- cli_result_t compilation_result = cli_runner_compiler_dump_tokens("../../examples/expression.ol");
- munit_assert_int(compilation_result.exec.exit_code, ==, 0);
- munit_assert_string_equal(compilation_result.exec.stdout_buf,
- "../../examples/expression.ol:1:1: <fn>\n"
- "../../examples/expression.ol:1:4: <identifier>\n"
- "../../examples/expression.ol:1:8: <(>\n"
- "../../examples/expression.ol:1:9: <)>\n"
- "../../examples/expression.ol:1:10: <:>\n"
- "../../examples/expression.ol:1:12: <identifier>\n"
- "../../examples/expression.ol:1:16: <{>\n"
- "../../examples/expression.ol:1:17: <line_feed>\n"
- "../../examples/expression.ol:2:3: <return>\n"
- "../../examples/expression.ol:2:10: <(>\n"
- "../../examples/expression.ol:2:11: <number>\n"
- "../../examples/expression.ol:2:14: <+>\n"
- "../../examples/expression.ol:2:16: <number>\n"
- "../../examples/expression.ol:2:18: <*>\n"
- "../../examples/expression.ol:2:20: <number>\n"
- "../../examples/expression.ol:2:21: <)>\n"
- "../../examples/expression.ol:2:23: <->\n"
- "../../examples/expression.ol:2:25: <(>\n"
- "../../examples/expression.ol:2:26: <number>\n"
- "../../examples/expression.ol:2:29: <->\n"
- "../../examples/expression.ol:2:31: <(>\n"
- "../../examples/expression.ol:2:32: <number>\n"
- "../../examples/expression.ol:2:34: <+>\n"
- "../../examples/expression.ol:2:36: <number>\n"
- "../../examples/expression.ol:2:37: <)>\n"
- "../../examples/expression.ol:2:39: </>\n"
- "../../examples/expression.ol:2:41: <number>\n"
- "../../examples/expression.ol:2:42: <)>\n"
- "../../examples/expression.ol:2:43: <line_feed>\n"
- "../../examples/expression.ol:3:1: <}>\n"
- "../../examples/expression.ol:3:2: <line_feed>\n"
- "../../examples/expression.ol:4:1: <EOF>\n");
- return MUNIT_OK;
-}
-
-static MunitResult
-test_cli_compile_minimal_program(const MunitParameter params[], void *user_data_or_fixture)
-{
- cli_result_t compilation_result = cli_runner_compiler_compile("../../examples/main_exit.ol");
- munit_assert_int(compilation_result.exec.exit_code, ==, 0);
-
- char *command_args[] = { compilation_result.binary_path, NULL };
-
- proc_exec_command_t command = { .path = command_args[0], .args = command_args };
-
- proc_exec(&command);
-
- remove(command_args[0]);
-
- munit_assert_int(command.result.exit_code, ==, 0);
-
- return MUNIT_OK;
-}
-
-static MunitTest tests[] = {
- { "/test_cli_dump_tokens_example_main_exit",
- test_cli_dump_tokens_example_main_exit,
- NULL,
- NULL,
- MUNIT_TEST_OPTION_NONE,
- NULL },
- { "/test_cli_dump_tokens_example_expression",
- test_cli_dump_tokens_example_expression,
- NULL,
- NULL,
- MUNIT_TEST_OPTION_NONE,
- NULL },
- { "/test_cli_compile_minimal_program", test_cli_compile_minimal_program, NULL, NULL, MUNIT_TEST_OPTION_NONE, NULL },
- { NULL, NULL, NULL, NULL, MUNIT_TEST_OPTION_NONE, NULL }
-};
-
-static const MunitSuite suite = { "/cli_test", tests, NULL, 1, MUNIT_SUITE_OPTION_NONE };
-
-int
-main(int argc, char *argv[])
-{
- return munit_suite_main(&suite, NULL, argc, argv);
- return EXIT_SUCCESS;
-}
diff --git a/tests/integration/proc_exec.c b/tests/integration/proc_exec.c
deleted file mode 100644
index c22dd1e..0000000
--- a/tests/integration/proc_exec.c
+++ /dev/null
@@ -1,63 +0,0 @@
-/*
- * Copyright (C) 2024 olang maintainers
- *
- * This program is free software: you can redistribute it and/or modify
- * it under the terms of the GNU General Public License as published by
- * the Free Software Foundation, either version 3 of the License, or
- * (at your option) any later version.
- *
- * This program is distributed in the hope that it will be useful,
- * but WITHOUT ANY WARRANTY; without even the implied warranty of
- * MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
- * GNU General Public License for more details.
- *
- * You should have received a copy of the GNU General Public License
- * along with this program. If not, see <https://www.gnu.org/licenses/>.
- */
-#include "proc_exec.h"
-#include <assert.h>
-#include <stdbool.h>
-#include <stdio.h>
-#include <stdlib.h>
-#include <string.h>
-#include <sys/wait.h>
-#include <unistd.h>
-
-
-void
-proc_exec(proc_exec_command_t* command)
-{
- int fd_pipe[2];
-
- if (pipe(fd_pipe) == -1) {
- perror("pipe error.");
- exit(1);
- }
-
- pid_t pid = fork();
-
- if (pid == -1) {
- perror("fork error.");
- exit(1);
- }
-
- if (pid == 0) {
- dup2(fd_pipe[1], STDOUT_FILENO);
- close(fd_pipe[0]);
- close(fd_pipe[1]);
-
- execv(command->path, command->args);
- perror("execl error.");
- exit(127);
- } else {
- close(fd_pipe[1]);
- // TODO: stop truncating the output.
- if (read(fd_pipe[0], command->result.stdout_buf, sizeof(command->result.stdout_buf)) == -1) {
- perror("read error.");
- exit(1);
- }
- int status;
- waitpid(pid, &status, 0);
- command->result.exit_code = WEXITSTATUS(status);
- }
-}
diff --git a/tests/integration/proc_exec.h b/tests/integration/proc_exec.h
deleted file mode 100644
index 45c2977..0000000
--- a/tests/integration/proc_exec.h
+++ /dev/null
@@ -1,37 +0,0 @@
-/*
- * Copyright (C) 2024 olang maintainers
- *
- * This program is free software: you can redistribute it and/or modify
- * it under the terms of the GNU General Public License as published by
- * the Free Software Foundation, either version 3 of the License, or
- * (at your option) any later version.
- *
- * This program is distributed in the hope that it will be useful,
- * but WITHOUT ANY WARRANTY; without even the implied warranty of
- * MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
- * GNU General Public License for more details.
- *
- * You should have received a copy of the GNU General Public License
- * along with this program. If not, see <https://www.gnu.org/licenses/>.
- */
-#ifndef PROC_EXEC_H
-#define PROC_EXEC_H
-#include <stdlib.h>
-
-typedef struct proc_exec_result
-{
- int exit_code;
- // FIXME: output buffer shouldn't be fixed size
- char stdout_buf[2048];
-} proc_exec_result_t;
-
-typedef struct proc_exec_command
-{
- char* path;
- char** args;
- proc_exec_result_t result;
-} proc_exec_command_t;
-
-void
-proc_exec(proc_exec_command_t* command);
-#endif
diff --git a/tests/integration/test.sh b/tests/integration/test.sh
index 6ab03de..9fdabef 100755
--- a/tests/integration/test.sh
+++ b/tests/integration/test.sh
@@ -1,3 +1,4 @@
+#!/bin/sh
COMPILER_PATH="../../olang"
TEST_FILE="$1"
@@ -15,57 +16,63 @@ TOKENS_EXPECT_OUTPUT_FILE="$TEST_FILE.test.expected_tokens_output"
TOKENS_OUTPUT_FILE="$TEST_FILE.test.tokens_output"
TOKENS_EXPECT_OUTPUT_FILE="$TEST_FILE.test.expected_tokens_output"
-PROGRAM_OUTPUT="$TEST_FILE.test.program_output"
-
+# Misc
extract_comment() {
tag="$1"
- comment="# $tag: "
- cat $TEST_FILE | grep "$comment" | sed -e "s/$comment//"
+ comment="# $tag:"
+ grep "$comment" "$TEST_FILE" | sed -e "s/$comment //"
+}
+
+cleanup() {
+ rm -f "$PROGRAM*"
}
# UI
COLOR_RED=1
COLOR_GREEN=2
COLOR_YELLOW=3
-COLOR_BLUE=4
COLOR_CYAN=6
COLOR_GRAY=7
colored() {
text="$1"
- color="$2"
+ color=$(tput setaf "$2")
+ reset=$(tput sgr0)
+
if [ -t 1 ]; then
- if tput setaf 1 &> /dev/null; then
- printf "$(tput setaf $color)$text$(tput sgr0)"
+ if tput setaf 1 > /dev/null 2>&1; then
+ printf "%s%s%s" "$color" "$text" "$reset"
return
fi
fi
- printf "$text"
+ printf "%s" "$text"
}
print_test_description() {
- colored "$TEST_FILE: \n" $COLOR_CYAN
- colored "$(extract_comment spec)\n\n" $COLOR_GRAY
+ colored "$TEST_FILE: " $COLOR_CYAN
+ printf "\n"
+ colored "$(extract_comment spec)" $COLOR_GRAY
+ printf "\n\n"
}
print_passed() {
context="$1"
- printf "$context: "
+ printf "%s: " "$context"
colored "passed" $COLOR_GREEN
echo
}
print_failed() {
context="$1"
- printf "$context: "
+ printf "%s: " "$context"
colored "failed" $COLOR_RED
echo
}
print_skiped() {
context="$1"
- printf "$context: "
+ printf "%s: " "$context"
colored "not set" $COLOR_GRAY
echo
}
@@ -98,7 +105,7 @@ expect_output() {
expected_file="$2"
actual_file="$3"
- if [ "$(cat $expected_file | wc -l)" = "0" ]; then
+ if [ "$(wc -l < "$expected_file")" = "0" ]; then
print_skiped "$context"
return
fi
@@ -107,7 +114,7 @@ expect_output() {
print_passed "$context"
else
if [ "$(cat "$expected_file")" = "%empty%" ]; then
- if [ "$(cat $actual_file | wc -c)" = "0" ]; then
+ if [ "$(wc -c < "$actual_file")" = "0" ]; then
print_passed "$context"
return
fi
@@ -119,19 +126,16 @@ expect_output() {
fi
}
-cleanup() {
- rm -f $PROGRAM*
-}
-
+# Tests
test_compiler() {
- $COMPILER_PATH $TEST_FILE -o $PROGRAM > "$COMPILER_OUTPUT_FILE" 2>&1
+ $COMPILER_PATH "$TEST_FILE" -o "$PROGRAM" > "$COMPILER_OUTPUT_FILE" 2>&1
EXIT=$?
EXPECTED_EXIT=$(extract_comment compiler_exit)
expect_exit_code compiler_exit "$EXPECTED_EXIT" "$EXIT"
- extract_comment compiler_output > $COMPILER_EXPECT_OUTPUT_FILE
+ extract_comment compiler_output > "$COMPILER_EXPECT_OUTPUT_FILE"
expect_output compiler_output "$COMPILER_EXPECT_OUTPUT_FILE" "$COMPILER_OUTPUT_FILE"
if [ "$EXIT" = "1" ]; then
@@ -142,25 +146,25 @@ test_compiler() {
}
test_ast() {
- $COMPILER_PATH $TEST_FILE --dump-ast > "$AST_OUTPUT_FILE" 2>&1
+ $COMPILER_PATH "$TEST_FILE" --dump-ast > "$AST_OUTPUT_FILE" 2>&1
- extract_comment ast > $AST_EXPECT_OUTPUT_FILE
+ extract_comment ast > "$AST_EXPECT_OUTPUT_FILE"
expect_output "ast" "$AST_EXPECT_OUTPUT_FILE" "$AST_OUTPUT_FILE"
}
test_tokens() {
- extract_comment tokens > $TOKENS_EXPECT_OUTPUT_FILE
- TOKEN_LINES=$(cat $TOKENS_EXPECT_OUTPUT_FILE | wc -l)
+ extract_comment tokens > "$TOKENS_EXPECT_OUTPUT_FILE"
+ TOKEN_LINES=$(wc -l < "$TOKENS_EXPECT_OUTPUT_FILE")
- $COMPILER_PATH $TEST_FILE --dump-tokens | head -n $TOKEN_LINES > "$TOKENS_OUTPUT_FILE" 2>&1
+ $COMPILER_PATH "$TEST_FILE" --dump-tokens | head -n "$TOKEN_LINES" > "$TOKENS_OUTPUT_FILE" 2>&1
- expect_output tokens $TOKENS_OUTPUT_FILE $TOKENS_EXPECT_OUTPUT_FILE
+ expect_output tokens "$TOKENS_OUTPUT_FILE" "$TOKENS_EXPECT_OUTPUT_FILE"
print_passed tokens
}
test_program() {
- ./$PROGRAM
+ "./$PROGRAM"
EXIT=$?
EXPECTED_EXIT=$(extract_comment program_exit)
--
2.34.1
^ permalink raw reply [flat|nested] 83+ messages in thread
* [PATCH olang 3/4] tests: include integration tests for function parser errors
2024-05-12 14:30 [PATCH olang 0/4] comment based integration tests Carlos Maniero
2024-05-12 14:30 ` [PATCH olang 1/4] tests: add comment based integration tests mechanism Carlos Maniero
2024-05-12 14:30 ` [PATCH olang 2/4] tests: remove previous integration tests structure Carlos Maniero
@ 2024-05-12 14:30 ` Carlos Maniero
2024-05-12 14:30 ` [PATCH olang 4/4] tests: print integration tests TODOs Carlos Maniero
` (2 subsequent siblings)
5 siblings, 0 replies; 83+ messages in thread
From: Carlos Maniero @ 2024-05-12 14:30 UTC (permalink / raw)
To: ~johnnyrichard/olang-devel; +Cc: Carlos Maniero
This new tests covers the parser errors we support.
Signed-off-by: Carlos Maniero <carlos@maniero.me>
---
tests/integration/tests/0002_fn_without_fn_keyword.ol | 8 ++++++++
tests/integration/tests/0003_fn_without_type.ol | 8 ++++++++
tests/integration/tests/0004_fn_without_type_colon.ol | 8 ++++++++
.../tests/0005_fn_without_open_curly_brackets.ol | 8 ++++++++
.../tests/0006_fn_without_close_curly_brackets.ol | 7 +++++++
tests/integration/tests/0007_fn_without_return.ol | 8 ++++++++
6 files changed, 47 insertions(+)
create mode 100644 tests/integration/tests/0002_fn_without_fn_keyword.ol
create mode 100644 tests/integration/tests/0003_fn_without_type.ol
create mode 100644 tests/integration/tests/0004_fn_without_type_colon.ol
create mode 100644 tests/integration/tests/0005_fn_without_open_curly_brackets.ol
create mode 100644 tests/integration/tests/0006_fn_without_close_curly_brackets.ol
create mode 100644 tests/integration/tests/0007_fn_without_return.ol
diff --git a/tests/integration/tests/0002_fn_without_fn_keyword.ol b/tests/integration/tests/0002_fn_without_fn_keyword.ol
new file mode 100644
index 0000000..f1ad57e
--- /dev/null
+++ b/tests/integration/tests/0002_fn_without_fn_keyword.ol
@@ -0,0 +1,8 @@
+# spec: An invalid program with no fn keyword
+main(): u32 {
+ return 0
+}
+# compiler_exit: 1
+# compiler_output: ./tests/0002_fn_without_fn_keyword.ol:2:1: error: got 'main' token but expect <fn>
+# compiler_output: main(): u32 {
+# compiler_output: ^
diff --git a/tests/integration/tests/0003_fn_without_type.ol b/tests/integration/tests/0003_fn_without_type.ol
new file mode 100644
index 0000000..32716e1
--- /dev/null
+++ b/tests/integration/tests/0003_fn_without_type.ol
@@ -0,0 +1,8 @@
+# spec: An invalid program with no type
+fn main(): {
+ return 0
+}
+# compiler_exit: 1
+# compiler_output: ./tests/0003_fn_without_type.ol:2:12: error: got '{' token but expect <identifier>
+# compiler_output: fn main(): {
+# compiler_output: ^
diff --git a/tests/integration/tests/0004_fn_without_type_colon.ol b/tests/integration/tests/0004_fn_without_type_colon.ol
new file mode 100644
index 0000000..bd04c37
--- /dev/null
+++ b/tests/integration/tests/0004_fn_without_type_colon.ol
@@ -0,0 +1,8 @@
+# spec: An invalid program with no type colon
+fn main() u32 {
+ return 0
+}
+# compiler_exit: 1
+# compiler_output: ./tests/0004_fn_without_type_colon.ol:2:11: error: got 'u32' token but expect <:>
+# compiler_output: fn main() u32 {
+# compiler_output: ^
diff --git a/tests/integration/tests/0005_fn_without_open_curly_brackets.ol b/tests/integration/tests/0005_fn_without_open_curly_brackets.ol
new file mode 100644
index 0000000..8e13946
--- /dev/null
+++ b/tests/integration/tests/0005_fn_without_open_curly_brackets.ol
@@ -0,0 +1,8 @@
+# spec: An invalid program with no open curly brackets
+fn main(): u32
+ return 0
+}
+# compiler_exit: 1
+# compiler_output: ./tests/0005_fn_without_open_curly_brackets.ol:3:3: error: got 'return' token but expect <{>
+# compiler_output: return 0
+# compiler_output: ^
diff --git a/tests/integration/tests/0006_fn_without_close_curly_brackets.ol b/tests/integration/tests/0006_fn_without_close_curly_brackets.ol
new file mode 100644
index 0000000..d43c9f9
--- /dev/null
+++ b/tests/integration/tests/0006_fn_without_close_curly_brackets.ol
@@ -0,0 +1,7 @@
+# spec: An invalid program with no close curly brackets
+fn main(): u32 {
+ return 0
+# compiler_exit: 1
+# compiler_output: ./tests/0006_fn_without_close_curly_brackets.ol:8:1: error: got '' token but expect <}>
+# compiler_output:
+# compiler_output: ^
diff --git a/tests/integration/tests/0007_fn_without_return.ol b/tests/integration/tests/0007_fn_without_return.ol
new file mode 100644
index 0000000..fe33d69
--- /dev/null
+++ b/tests/integration/tests/0007_fn_without_return.ol
@@ -0,0 +1,8 @@
+# spec: An invalid program without return statment
+# TODO: Improve the compiler error message
+fn main(): u32 {
+}
+# compiler_exit: 1
+# compiler_output: ./tests/0007_fn_without_return.ol:4:1: error: got '}' token but expect <return>
+# compiler_output: }
+# compiler_output: ^
--
2.34.1
^ permalink raw reply [flat|nested] 83+ messages in thread
* [PATCH olang 4/4] tests: print integration tests TODOs
2024-05-12 14:30 [PATCH olang 0/4] comment based integration tests Carlos Maniero
` (2 preceding siblings ...)
2024-05-12 14:30 ` [PATCH olang 3/4] tests: include integration tests for function parser errors Carlos Maniero
@ 2024-05-12 14:30 ` Carlos Maniero
2024-05-12 14:31 ` [olang/patches/.build.yml] build success builds.sr.ht
2024-08-09 19:42 ` [PATCH olang 0/4] comment based integration tests Johnny Richard
2024-08-21 15:58 ` Johnny Richard
5 siblings, 1 reply; 83+ messages in thread
From: Carlos Maniero @ 2024-05-12 14:30 UTC (permalink / raw)
To: ~johnnyrichard/olang-devel; +Cc: Carlos Maniero
Sometimes people use to ask how to contribute with olang. This is a
great way to help them, we can just create TODOS on the integration
tests as we already have some parts of the language specified.
Signed-off-by: Carlos Maniero <carlos@maniero.me>
---
tests/integration/test.sh | 9 +++++++++
1 file changed, 9 insertions(+)
diff --git a/tests/integration/test.sh b/tests/integration/test.sh
index 9fdabef..c8535a7 100755
--- a/tests/integration/test.sh
+++ b/tests/integration/test.sh
@@ -56,6 +56,14 @@ print_test_description() {
printf "\n\n"
}
+print_todo() {
+ TODOS=$(extract_comment TODO)
+
+ if [ -n "$TODOS" ]; then
+ colored "TODO: $(extract_comment TODO)\n\n" $COLOR_YELLOW
+ fi
+}
+
print_passed() {
context="$1"
printf "%s: " "$context"
@@ -174,6 +182,7 @@ test_program() {
main() {
print_test_description
+ print_todo
test_compiler
test_program
--
2.34.1
^ permalink raw reply [flat|nested] 83+ messages in thread
* [olang/patches/.build.yml] build success
2024-05-12 14:30 ` [PATCH olang 4/4] tests: print integration tests TODOs Carlos Maniero
@ 2024-05-12 14:31 ` builds.sr.ht
0 siblings, 0 replies; 83+ messages in thread
From: builds.sr.ht @ 2024-05-12 14:31 UTC (permalink / raw)
To: Carlos Maniero; +Cc: ~johnnyrichard/olang-devel
olang/patches/.build.yml: SUCCESS in 51s
[comment based integration tests][0] from [Carlos Maniero][1]
[0]: https://lists.sr.ht/~johnnyrichard/olang-devel/patches/51804
[1]: mailto:carlos@maniero.me
✓ #1219016 SUCCESS olang/patches/.build.yml https://builds.sr.ht/~johnnyrichard/job/1219016
^ permalink raw reply [flat|nested] 83+ messages in thread
* Re: [PATCH olang 0/4] comment based integration tests
2024-05-12 14:30 [PATCH olang 0/4] comment based integration tests Carlos Maniero
` (3 preceding siblings ...)
2024-05-12 14:30 ` [PATCH olang 4/4] tests: print integration tests TODOs Carlos Maniero
@ 2024-08-09 19:42 ` Johnny Richard
2024-08-21 15:58 ` Johnny Richard
5 siblings, 0 replies; 83+ messages in thread
From: Johnny Richard @ 2024-08-09 19:42 UTC (permalink / raw)
To: Carlos Maniero; +Cc: ~johnnyrichard/olang-devel
Thanks a lot for this contribution, I think it will improve the
development experience and definitely will help us to move forward
faster.
I have only a small adjustment to suggest, actually a nitpick.
On Sun, May 12, 2024 at 11:30:29AM GMT, Carlos Maniero wrote:
> The old munit based integration tests was replaced by a new mechanism
> that makes testing more tasteful and easy to perform.
>
> To create an integration tests you just need to create a olang file at
> *tests/integration/tests* directory. The assertions are performed
> thought a couple of comments.
The folder *tests/integration/tests* feels a little bit redundant. What
do you think about changing the folder structure to a smaller one like
*test/integration*?
^ permalink raw reply [flat|nested] 83+ messages in thread
* Re: [PATCH olang 0/4] comment based integration tests
2024-05-12 14:30 [PATCH olang 0/4] comment based integration tests Carlos Maniero
` (4 preceding siblings ...)
2024-08-09 19:42 ` [PATCH olang 0/4] comment based integration tests Johnny Richard
@ 2024-08-21 15:58 ` Johnny Richard
5 siblings, 0 replies; 83+ messages in thread
From: Johnny Richard @ 2024-08-21 15:58 UTC (permalink / raw)
To: Carlos Maniero; +Cc: ~johnnyrichard/olang-devel
This patch has been rejected. Actually there is another patch which
has superseded this one.
^ permalink raw reply [flat|nested] 83+ messages in thread
* [olang/patches/.build.yml] build success
2024-09-27 23:07 [PATCH olang v2 1/2] ast: add function call node Johnny Richard
@ 2024-09-27 21:11 ` builds.sr.ht
0 siblings, 0 replies; 83+ messages in thread
From: builds.sr.ht @ 2024-09-27 21:11 UTC (permalink / raw)
To: Johnny Richard; +Cc: ~johnnyrichard/olang-devel
olang/patches/.build.yml: SUCCESS in 19s
[frontend: Add function calls parsing][0] v2 from [Johnny Richard][1]
[0]: https://lists.sr.ht/~johnnyrichard/olang-devel/patches/55225
[1]: mailto:johnny@johnnyrichard.com
✓ #1338817 SUCCESS olang/patches/.build.yml https://builds.sr.ht/~johnnyrichard/job/1338817
^ permalink raw reply [flat|nested] 83+ messages in thread
* [olang/patches/.build.yml] build success
2024-09-25 23:20 [PATCH olang v1 2/2] parser: add support for parsing function calls Johnny Richard
@ 2024-09-25 21:22 ` builds.sr.ht
0 siblings, 0 replies; 83+ messages in thread
From: builds.sr.ht @ 2024-09-25 21:22 UTC (permalink / raw)
To: Johnny Richard; +Cc: ~johnnyrichard/olang-devel
olang/patches/.build.yml: SUCCESS in 20s
[frontend: Add function calls parsing][0] from [Johnny Richard][1]
[0]: https://lists.sr.ht/~johnnyrichard/olang-devel/patches/55199
[1]: mailto:johnny@johnnyrichard.com
✓ #1337043 SUCCESS olang/patches/.build.yml https://builds.sr.ht/~johnnyrichard/job/1337043
^ permalink raw reply [flat|nested] 83+ messages in thread
* [olang/patches/.build.yml] build success
2024-09-25 18:39 [PATCH olang] tests: fix diff error output Carlos Maniero
@ 2024-09-25 18:39 ` builds.sr.ht
0 siblings, 0 replies; 83+ messages in thread
From: builds.sr.ht @ 2024-09-25 18:39 UTC (permalink / raw)
To: Carlos Maniero; +Cc: ~johnnyrichard/olang-devel
olang/patches/.build.yml: SUCCESS in 19s
[tests: fix diff error output][0] from [Carlos Maniero][1]
[0]: https://lists.sr.ht/~johnnyrichard/olang-devel/patches/55198
[1]: mailto:carlos@maniero.me
✓ #1336951 SUCCESS olang/patches/.build.yml https://builds.sr.ht/~johnnyrichard/job/1336951
^ permalink raw reply [flat|nested] 83+ messages in thread
* [olang/patches/.build.yml] build success
2024-09-25 18:30 [PATCH olang] parser: parse multiple function into a single translation unit Carlos Maniero
@ 2024-09-25 18:31 ` builds.sr.ht
0 siblings, 0 replies; 83+ messages in thread
From: builds.sr.ht @ 2024-09-25 18:31 UTC (permalink / raw)
To: Carlos Maniero; +Cc: ~johnnyrichard/olang-devel
olang/patches/.build.yml: SUCCESS in 19s
[parser: parse multiple function into a single translation unit][0] from [Carlos Maniero][1]
[0]: https://lists.sr.ht/~johnnyrichard/olang-devel/patches/55197
[1]: mailto:carlos@maniero.me
✓ #1336943 SUCCESS olang/patches/.build.yml https://builds.sr.ht/~johnnyrichard/job/1336943
^ permalink raw reply [flat|nested] 83+ messages in thread
* [olang/patches/.build.yml] build success
2024-09-23 22:19 [PATCH olang v1 2/3] lexer: add token comma Johnny Richard
@ 2024-09-23 22:23 ` builds.sr.ht
0 siblings, 0 replies; 83+ messages in thread
From: builds.sr.ht @ 2024-09-23 22:23 UTC (permalink / raw)
To: Johnny Richard; +Cc: ~johnnyrichard/olang-devel
olang/patches/.build.yml: SUCCESS in 19s
[parse function definition params][0] from [Johnny Richard][1]
[0]: https://lists.sr.ht/~johnnyrichard/olang-devel/patches/55183
[1]: mailto:johnny@johnnyrichard.com
✓ #1335469 SUCCESS olang/patches/.build.yml https://builds.sr.ht/~johnnyrichard/job/1335469
^ permalink raw reply [flat|nested] 83+ messages in thread
* [olang/patches/.build.yml] build success
2024-09-23 11:43 [PATCH olang 2/2] ast: permit multi declarations on translation unit Carlos Maniero
@ 2024-09-23 11:44 ` builds.sr.ht
0 siblings, 0 replies; 83+ messages in thread
From: builds.sr.ht @ 2024-09-23 11:44 UTC (permalink / raw)
To: Carlos Maniero; +Cc: ~johnnyrichard/olang-devel
olang/patches/.build.yml: SUCCESS in 20s
[Rename program to translation unit][0] from [Carlos Maniero][1]
[0]: https://lists.sr.ht/~johnnyrichard/olang-devel/patches/55177
[1]: mailto:carlos@maniero.me
✓ #1335028 SUCCESS olang/patches/.build.yml https://builds.sr.ht/~johnnyrichard/job/1335028
^ permalink raw reply [flat|nested] 83+ messages in thread
* [olang/patches/.build.yml] build success
2024-09-23 10:11 [PATCH olang v1 3/3] naming: rename all identifier symbols to id Carlos Maniero
@ 2024-09-23 10:12 ` builds.sr.ht
0 siblings, 0 replies; 83+ messages in thread
From: builds.sr.ht @ 2024-09-23 10:12 UTC (permalink / raw)
To: Carlos Maniero; +Cc: ~johnnyrichard/olang-devel
olang/patches/.build.yml: SUCCESS in 19s
[Housekeeping: resolve a few FIXMEs related to code style][0] from [Carlos Maniero][1]
[0]: https://lists.sr.ht/~johnnyrichard/olang-devel/patches/55176
[1]: mailto:carlos@maniero.me
✓ #1334988 SUCCESS olang/patches/.build.yml https://builds.sr.ht/~johnnyrichard/job/1334988
^ permalink raw reply [flat|nested] 83+ messages in thread
* [olang/patches/.build.yml] build success
2024-09-22 0:46 [PATCH olang v2 4/4] codegen: operate mov instructions based on the symbol's type Carlos Maniero
@ 2024-09-22 0:47 ` builds.sr.ht
0 siblings, 0 replies; 83+ messages in thread
From: builds.sr.ht @ 2024-09-22 0:47 UTC (permalink / raw)
To: Carlos Maniero; +Cc: ~johnnyrichard/olang-devel
olang/patches/.build.yml: SUCCESS in 20s
[extend unsined integers types (u8, u16, u64)][0] v2 from [Carlos Maniero][1]
[0]: https://lists.sr.ht/~johnnyrichard/olang-devel/patches/55161
[1]: mailto:carlos@maniero.me
✓ #1334228 SUCCESS olang/patches/.build.yml https://builds.sr.ht/~johnnyrichard/job/1334228
^ permalink raw reply [flat|nested] 83+ messages in thread
* [olang/patches/.build.yml] build success
2024-09-21 21:02 [PATCH olang v1 2/2] tests: build: add parallelization support for unit tests Johnny Richard
@ 2024-09-21 21:05 ` builds.sr.ht
0 siblings, 0 replies; 83+ messages in thread
From: builds.sr.ht @ 2024-09-21 21:05 UTC (permalink / raw)
To: Johnny Richard; +Cc: ~johnnyrichard/olang-devel
olang/patches/.build.yml: SUCCESS in 20s
[tests: build: improve makefile for tests][0] from [Johnny Richard][1]
[0]: https://lists.sr.ht/~johnnyrichard/olang-devel/patches/55158
[1]: mailto:johnny@johnnyrichard.com
✓ #1334090 SUCCESS olang/patches/.build.yml https://builds.sr.ht/~johnnyrichard/job/1334090
^ permalink raw reply [flat|nested] 83+ messages in thread
* [olang/patches/.build.yml] build success
2024-09-21 8:25 [PATCH olang 5/5] codegen: perform mov instructions based on variable type Carlos Maniero
@ 2024-09-21 8:26 ` builds.sr.ht
0 siblings, 0 replies; 83+ messages in thread
From: builds.sr.ht @ 2024-09-21 8:26 UTC (permalink / raw)
To: Carlos Maniero; +Cc: ~johnnyrichard/olang-devel
olang/patches/.build.yml: SUCCESS in 21s
[extend unsined integers types (u8, u16, u64)][0] from [Carlos Maniero][1]
[0]: https://lists.sr.ht/~johnnyrichard/olang-devel/patches/55142
[1]: mailto:carlos@maniero.me
✓ #1333732 SUCCESS olang/patches/.build.yml https://builds.sr.ht/~johnnyrichard/job/1333732
^ permalink raw reply [flat|nested] 83+ messages in thread
* [olang/patches/.build.yml] build success
2024-09-21 1:13 [PATCH olang 5/5] codegen: preserve function's variable stack location Carlos Maniero
@ 2024-09-21 1:13 ` builds.sr.ht
0 siblings, 0 replies; 83+ messages in thread
From: builds.sr.ht @ 2024-09-21 1:13 UTC (permalink / raw)
To: Carlos Maniero; +Cc: ~johnnyrichard/olang-devel
olang/patches/.build.yml: SUCCESS in 20s
[fix multiple variables][0] from [Carlos Maniero][1]
[0]: https://lists.sr.ht/~johnnyrichard/olang-devel/patches/55133
[1]: mailto:carlos@maniero.me
✓ #1333568 SUCCESS olang/patches/.build.yml https://builds.sr.ht/~johnnyrichard/job/1333568
^ permalink raw reply [flat|nested] 83+ messages in thread
* [olang/patches/.build.yml] build success
2024-09-21 0:20 [PATCH olang v1 3/3] codegen: add support scopes and symbols lookups for var Johnny Richard
@ 2024-09-21 0:23 ` builds.sr.ht
0 siblings, 0 replies; 83+ messages in thread
From: builds.sr.ht @ 2024-09-21 0:23 UTC (permalink / raw)
To: Johnny Richard; +Cc: ~johnnyrichard/olang-devel
olang/patches/.build.yml: SUCCESS in 21s
[compiler: enable full compilation for vars][0] from [Johnny Richard][1]
[0]: https://lists.sr.ht/~johnnyrichard/olang-devel/patches/55131
[1]: mailto:johnny@johnnyrichard.com
✓ #1333519 SUCCESS olang/patches/.build.yml https://builds.sr.ht/~johnnyrichard/job/1333519
^ permalink raw reply [flat|nested] 83+ messages in thread
* [olang/patches/.build.yml] build success
2024-09-17 15:14 [PATCH olang] cli: add libc error handling Carlos Maniero
@ 2024-09-17 15:15 ` builds.sr.ht
0 siblings, 0 replies; 83+ messages in thread
From: builds.sr.ht @ 2024-09-17 15:15 UTC (permalink / raw)
To: Carlos Maniero; +Cc: ~johnnyrichard/olang-devel
olang/patches/.build.yml: SUCCESS in 20s
[cli: add libc error handling][0] from [Carlos Maniero][1]
[0]: https://lists.sr.ht/~johnnyrichard/olang-devel/patches/55079
[1]: mailto:carlos@maniero.me
✓ #1330161 SUCCESS olang/patches/.build.yml https://builds.sr.ht/~johnnyrichard/job/1330161
^ permalink raw reply [flat|nested] 83+ messages in thread
* [olang/patches/.build.yml] build success
2024-09-17 13:43 [PATCH olang v1] remove unused examples programs Johnny Richard
@ 2024-09-17 11:43 ` builds.sr.ht
0 siblings, 0 replies; 83+ messages in thread
From: builds.sr.ht @ 2024-09-17 11:43 UTC (permalink / raw)
To: Johnny Richard; +Cc: ~johnnyrichard/olang-devel
olang/patches/.build.yml: SUCCESS in 20s
[remove unused examples programs][0] from [Johnny Richard][1]
[0]: https://lists.sr.ht/~johnnyrichard/olang-devel/patches/55077
[1]: mailto:johnny@johnnyrichard.com
✓ #1329949 SUCCESS olang/patches/.build.yml https://builds.sr.ht/~johnnyrichard/job/1329949
^ permalink raw reply [flat|nested] 83+ messages in thread
* [olang/patches/.build.yml] build success
2024-09-17 12:46 [PATCH olang v1 4/4] docs: info: add instructions to install/uninstall olang Johnny Richard
@ 2024-09-17 10:48 ` builds.sr.ht
0 siblings, 0 replies; 83+ messages in thread
From: builds.sr.ht @ 2024-09-17 10:48 UTC (permalink / raw)
To: Johnny Richard; +Cc: ~johnnyrichard/olang-devel
olang/patches/.build.yml: SUCCESS in 20s
[build: add install and uninstall targets][0] from [Johnny Richard][1]
[0]: https://lists.sr.ht/~johnnyrichard/olang-devel/patches/55076
[1]: mailto:johnny@johnnyrichard.com
✓ #1329923 SUCCESS olang/patches/.build.yml https://builds.sr.ht/~johnnyrichard/job/1329923
^ permalink raw reply [flat|nested] 83+ messages in thread
* [olang/patches/.build.yml] build success
2024-09-16 16:29 [PATCH olang v1 3/3] docs: remove pandoc dependency for man docs Johnny Richard
@ 2024-09-16 14:31 ` builds.sr.ht
0 siblings, 0 replies; 83+ messages in thread
From: builds.sr.ht @ 2024-09-16 14:31 UTC (permalink / raw)
To: Johnny Richard; +Cc: ~johnnyrichard/olang-devel
olang/patches/.build.yml: SUCCESS in 50s
[docs: remove pandoc dependency ][0] from [Johnny Richard][1]
[0]: https://lists.sr.ht/~johnnyrichard/olang-devel/patches/55062
[1]: mailto:johnny@johnnyrichard.com
✓ #1329317 SUCCESS olang/patches/.build.yml https://builds.sr.ht/~johnnyrichard/job/1329317
^ permalink raw reply [flat|nested] 83+ messages in thread
* [olang/patches/.build.yml] build success
2024-09-11 1:03 [PATCH olang v1 2/2] parser: add var definition and reference support Johnny Richard
@ 2024-09-10 23:05 ` builds.sr.ht
0 siblings, 0 replies; 83+ messages in thread
From: builds.sr.ht @ 2024-09-10 23:05 UTC (permalink / raw)
To: Johnny Richard; +Cc: ~johnnyrichard/olang-devel
olang/patches/.build.yml: SUCCESS in 35s
[parser: implement variable definition][0] from [Johnny Richard][1]
[0]: https://lists.sr.ht/~johnnyrichard/olang-devel/patches/54983
[1]: mailto:johnny@johnnyrichard.com
✓ #1324659 SUCCESS olang/patches/.build.yml https://builds.sr.ht/~johnnyrichard/job/1324659
^ permalink raw reply [flat|nested] 83+ messages in thread
* [olang/patches/.build.yml] build success
2024-08-25 13:16 [PATCH olang v2 2/2] codegen: x86_64: implement binary operations Johnny Richard
@ 2024-08-25 13:26 ` builds.sr.ht
0 siblings, 0 replies; 83+ messages in thread
From: builds.sr.ht @ 2024-08-25 13:26 UTC (permalink / raw)
To: Johnny Richard; +Cc: ~johnnyrichard/olang-devel
olang/patches/.build.yml: SUCCESS in 37s
[codegen: x86_64: implement binary operations][0] v2 from [Johnny Richard][1]
[0]: https://lists.sr.ht/~johnnyrichard/olang-devel/patches/54696
[1]: mailto:johnny@johnnyrichard.com
✓ #1311572 SUCCESS olang/patches/.build.yml https://builds.sr.ht/~johnnyrichard/job/1311572
^ permalink raw reply [flat|nested] 83+ messages in thread
* [olang/patches/.build.yml] build success
2024-08-21 3:39 [PATCH olang 1/2] tests: add comment based integration tests mechanism Carlos Maniero
@ 2024-08-21 3:41 ` builds.sr.ht
0 siblings, 0 replies; 83+ messages in thread
From: builds.sr.ht @ 2024-08-21 3:41 UTC (permalink / raw)
To: Carlos Maniero; +Cc: ~johnnyrichard/olang-devel
olang/patches/.build.yml: SUCCESS in 36s
[tests: create a text-based integrations test][0] from [Carlos Maniero][1]
[0]: https://lists.sr.ht/~johnnyrichard/olang-devel/patches/54588
[1]: mailto:carlos@maniero.me
✓ #1308300 SUCCESS olang/patches/.build.yml https://builds.sr.ht/~johnnyrichard/job/1308300
^ permalink raw reply [flat|nested] 83+ messages in thread
* [olang/patches/.build.yml] build success
2024-08-13 18:55 [PATCH olang v2 2/2] ast: inline ast_node_data_t union typedef Johnny Richard
@ 2024-08-13 18:04 ` builds.sr.ht
0 siblings, 0 replies; 83+ messages in thread
From: builds.sr.ht @ 2024-08-13 18:04 UTC (permalink / raw)
To: Johnny Richard; +Cc: ~johnnyrichard/olang-devel
olang/patches/.build.yml: SUCCESS in 32s
[ast: refactor: inline union typedefs][0] v2 from [Johnny Richard][1]
[0]: https://lists.sr.ht/~johnnyrichard/olang-devel/patches/54447
[1]: mailto:johnny@johnnyrichard.com
✓ #1302393 SUCCESS olang/patches/.build.yml https://builds.sr.ht/~johnnyrichard/job/1302393
^ permalink raw reply [flat|nested] 83+ messages in thread
* [olang/patches/.build.yml] build success
2024-04-27 12:14 [PATCH olang v1 2/2] codegen: x86_64: implement binary operations Johnny Richard
@ 2024-04-27 11:21 ` builds.sr.ht
0 siblings, 0 replies; 83+ messages in thread
From: builds.sr.ht @ 2024-04-27 11:21 UTC (permalink / raw)
To: Johnny Richard; +Cc: ~johnnyrichard/olang-devel
olang/patches/.build.yml: SUCCESS in 43s
[codegen: x86_64: implement binary operations][0] from [Johnny Richard][1]
[0]: https://lists.sr.ht/~johnnyrichard/olang-devel/patches/51409
[1]: mailto:johnny@johnnyrichard.com
✓ #1206119 SUCCESS olang/patches/.build.yml https://builds.sr.ht/~johnnyrichard/job/1206119
^ permalink raw reply [flat|nested] 83+ messages in thread
* [olang/patches/.build.yml] build success
2024-04-18 23:08 [PATCH olang v1] parser: fix parse expression with binop chain Johnny Richard
@ 2024-04-18 22:11 ` builds.sr.ht
0 siblings, 0 replies; 83+ messages in thread
From: builds.sr.ht @ 2024-04-18 22:11 UTC (permalink / raw)
To: Johnny Richard; +Cc: ~johnnyrichard/olang-devel
olang/patches/.build.yml: SUCCESS in 47s
[parser: fix parse expression with binop chain][0] from [Johnny Richard][1]
[0]: https://lists.sr.ht/~johnnyrichard/olang-devel/patches/51128
[1]: mailto:johnny@johnnyrichard.com
✓ #1199392 SUCCESS olang/patches/.build.yml https://builds.sr.ht/~johnnyrichard/job/1199392
^ permalink raw reply [flat|nested] 83+ messages in thread
* [olang/patches/.build.yml] build success
2024-04-18 22:18 [PATCH olang v1] parser: add missing <= and >= binary operators Johnny Richard
@ 2024-04-18 21:22 ` builds.sr.ht
0 siblings, 0 replies; 83+ messages in thread
From: builds.sr.ht @ 2024-04-18 21:22 UTC (permalink / raw)
To: Johnny Richard; +Cc: ~johnnyrichard/olang-devel
olang/patches/.build.yml: SUCCESS in 43s
[parser: add missing <= and >= binary operators][0] from [Johnny Richard][1]
[0]: https://lists.sr.ht/~johnnyrichard/olang-devel/patches/51123
[1]: mailto:johnny@johnnyrichard.com
✓ #1199375 SUCCESS olang/patches/.build.yml https://builds.sr.ht/~johnnyrichard/job/1199375
^ permalink raw reply [flat|nested] 83+ messages in thread
* [olang/patches/.build.yml] build success
2024-04-18 21:58 [PATCH olang v1] docs: spec: add %, <= and >= binary operators Johnny Richard
@ 2024-04-18 21:02 ` builds.sr.ht
0 siblings, 0 replies; 83+ messages in thread
From: builds.sr.ht @ 2024-04-18 21:02 UTC (permalink / raw)
To: Johnny Richard; +Cc: ~johnnyrichard/olang-devel
olang/patches/.build.yml: SUCCESS in 44s
[docs: spec: add %, <= and >= binary operators][0] from [Johnny Richard][1]
[0]: https://lists.sr.ht/~johnnyrichard/olang-devel/patches/51122
[1]: mailto:johnny@johnnyrichard.com
✓ #1199362 SUCCESS olang/patches/.build.yml https://builds.sr.ht/~johnnyrichard/job/1199362
^ permalink raw reply [flat|nested] 83+ messages in thread
* [olang/patches/.build.yml] build success
2024-04-16 23:51 [PATCH olang v1] Revert "docs: spec: postpone assignment operators" Johnny Richard
@ 2024-04-16 22:56 ` builds.sr.ht
0 siblings, 0 replies; 83+ messages in thread
From: builds.sr.ht @ 2024-04-16 22:56 UTC (permalink / raw)
To: Johnny Richard; +Cc: ~johnnyrichard/olang-devel
olang/patches/.build.yml: SUCCESS in 43s
[Revert "docs: spec: postpone assignment operators"][0] from [Johnny Richard][1]
[0]: https://lists.sr.ht/~johnnyrichard/olang-devel/patches/51078
[1]: mailto:johnny@johnnyrichard.com
✓ #1197726 SUCCESS olang/patches/.build.yml https://builds.sr.ht/~johnnyrichard/job/1197726
^ permalink raw reply [flat|nested] 83+ messages in thread
* [olang/patches/.build.yml] build success
2024-04-16 23:35 [PATCH olang v2] docs: spec: add binary expressions Johnny Richard
@ 2024-04-16 22:40 ` builds.sr.ht
0 siblings, 0 replies; 83+ messages in thread
From: builds.sr.ht @ 2024-04-16 22:40 UTC (permalink / raw)
To: Johnny Richard; +Cc: ~johnnyrichard/olang-devel
olang/patches/.build.yml: SUCCESS in 44s
[docs: spec: add binary expressions][0] v2 from [Johnny Richard][1]
[0]: https://lists.sr.ht/~johnnyrichard/olang-devel/patches/51076
[1]: mailto:johnny@johnnyrichard.com
✓ #1197709 SUCCESS olang/patches/.build.yml https://builds.sr.ht/~johnnyrichard/job/1197709
^ permalink raw reply [flat|nested] 83+ messages in thread
* [olang/patches/.build.yml] build success
2024-04-15 18:20 [PATCH olang v1] spec: ebnf: add binary expressions Johnny Richard
@ 2024-04-15 17:43 ` builds.sr.ht
0 siblings, 0 replies; 83+ messages in thread
From: builds.sr.ht @ 2024-04-15 17:43 UTC (permalink / raw)
To: Johnny Richard; +Cc: ~johnnyrichard/olang-devel
olang/patches/.build.yml: SUCCESS in 44s
[spec: ebnf: add binary expressions][0] from [Johnny Richard][1]
[0]: https://lists.sr.ht/~johnnyrichard/olang-devel/patches/51036
[1]: mailto:johnny@johnnyrichard.com
✓ #1196562 SUCCESS olang/patches/.build.yml https://builds.sr.ht/~johnnyrichard/job/1196562
^ permalink raw reply [flat|nested] 83+ messages in thread
* [olang/patches/.build.yml] build success
2024-04-08 4:38 [PATCH olang v2 2/2] docs: spec: add variables and constants specification Carlos Maniero
@ 2024-04-08 4:39 ` builds.sr.ht
0 siblings, 0 replies; 83+ messages in thread
From: builds.sr.ht @ 2024-04-08 4:39 UTC (permalink / raw)
To: Carlos Maniero; +Cc: ~johnnyrichard/olang-devel
olang/patches/.build.yml: SUCCESS in 39s
[docs: variables specification][0] v2 from [Carlos Maniero][1]
[0]: https://lists.sr.ht/~johnnyrichard/olang-devel/patches/50820
[1]: mailto:carlos@maniero.me
✓ #1189894 SUCCESS olang/patches/.build.yml https://builds.sr.ht/~johnnyrichard/job/1189894
^ permalink raw reply [flat|nested] 83+ messages in thread
* [olang/patches/.build.yml] build success
2024-03-29 1:59 [PATCH olang] linter: turn off clang-format to keep retro compatibility with v16 Johnny Richard
@ 2024-03-29 0:59 ` builds.sr.ht
0 siblings, 0 replies; 83+ messages in thread
From: builds.sr.ht @ 2024-03-29 0:59 UTC (permalink / raw)
To: Johnny Richard; +Cc: ~johnnyrichard/olang-devel
olang/patches/.build.yml: SUCCESS in 37s
[linter: turn off clang-format to keep retro compatibility with v16][0] from [Johnny Richard][1]
[0]: https://lists.sr.ht/~johnnyrichard/olang-devel/patches/50521
[1]: mailto:johnny@johnnyrichard.com
✓ #1181503 SUCCESS olang/patches/.build.yml https://builds.sr.ht/~johnnyrichard/job/1181503
^ permalink raw reply [flat|nested] 83+ messages in thread
* [olang/patches/.build.yml] build success
2024-03-29 0:33 [PATCH olang] site: change look and feel and rewrite home introduction section Johnny Richard
@ 2024-03-28 23:33 ` builds.sr.ht
0 siblings, 0 replies; 83+ messages in thread
From: builds.sr.ht @ 2024-03-28 23:33 UTC (permalink / raw)
To: Johnny Richard; +Cc: ~johnnyrichard/olang-devel
olang/patches/.build.yml: SUCCESS in 38s
[site: change look and feel and rewrite home introduction section][0] from [Johnny Richard][1]
[0]: https://lists.sr.ht/~johnnyrichard/olang-devel/patches/50517
[1]: mailto:johnny@johnnyrichard.com
✓ #1181439 SUCCESS olang/patches/.build.yml https://builds.sr.ht/~johnnyrichard/job/1181439
^ permalink raw reply [flat|nested] 83+ messages in thread
* [olang/patches/.build.yml] build success
2024-03-24 16:12 [PATCH olang v3] docs: create o programming language spec Johnny Richard
@ 2024-03-24 15:16 ` builds.sr.ht
0 siblings, 0 replies; 83+ messages in thread
From: builds.sr.ht @ 2024-03-24 15:16 UTC (permalink / raw)
To: Johnny Richard; +Cc: ~johnnyrichard/olang-devel
olang/patches/.build.yml: SUCCESS in 40s
[docs: create o programming language spec][0] v3 from [Johnny Richard][1]
[0]: https://lists.sr.ht/~johnnyrichard/olang-devel/patches/50408
[1]: mailto:johnny@johnnyrichard.com
✓ #1177304 SUCCESS olang/patches/.build.yml https://builds.sr.ht/~johnnyrichard/job/1177304
^ permalink raw reply [flat|nested] 83+ messages in thread
* [olang/patches/.build.yml] build success
2024-03-19 20:18 [PATCH olang v2] docs: create o programming language spec Johnny Richard
@ 2024-03-19 19:20 ` builds.sr.ht
0 siblings, 0 replies; 83+ messages in thread
From: builds.sr.ht @ 2024-03-19 19:20 UTC (permalink / raw)
To: Johnny Richard; +Cc: ~johnnyrichard/olang-devel
olang/patches/.build.yml: SUCCESS in 39s
[docs: create o programming language spec][0] v2 from [Johnny Richard][1]
[0]: https://lists.sr.ht/~johnnyrichard/olang-devel/patches/50320
[1]: mailto:johnny@johnnyrichard.com
✓ #1173074 SUCCESS olang/patches/.build.yml https://builds.sr.ht/~johnnyrichard/job/1173074
^ permalink raw reply [flat|nested] 83+ messages in thread
* [olang/patches/.build.yml] build success
2024-03-19 19:57 [PATCH olang v1 3/3] codegen: add compiler support to linux aarch64 arch Johnny Richard
@ 2024-03-19 19:00 ` builds.sr.ht
0 siblings, 0 replies; 83+ messages in thread
From: builds.sr.ht @ 2024-03-19 19:00 UTC (permalink / raw)
To: Johnny Richard; +Cc: ~johnnyrichard/olang-devel
olang/patches/.build.yml: SUCCESS in 38s
[fe: add compiler support to linux aarch64][0] from [Johnny Richard][1]
[0]: https://lists.sr.ht/~johnnyrichard/olang-devel/patches/50318
[1]: mailto:johnny@johnnyrichard.com
✓ #1173054 SUCCESS olang/patches/.build.yml https://builds.sr.ht/~johnnyrichard/job/1173054
^ permalink raw reply [flat|nested] 83+ messages in thread
* [olang/patches/.build.yml] build success
2024-03-18 8:39 [PATCH olang v3 3/3] parser: add all binary operation expressions Johnny Richard
@ 2024-03-18 7:43 ` builds.sr.ht
0 siblings, 0 replies; 83+ messages in thread
From: builds.sr.ht @ 2024-03-18 7:43 UTC (permalink / raw)
To: Johnny Richard; +Cc: ~johnnyrichard/olang-devel
olang/patches/.build.yml: SUCCESS in 40s
[fe: add binary operation expr support][0] v3 from [Johnny Richard][1]
[0]: https://lists.sr.ht/~johnnyrichard/olang-devel/patches/50288
[1]: mailto:johnny@johnnyrichard.com
✓ #1171874 SUCCESS olang/patches/.build.yml https://builds.sr.ht/~johnnyrichard/job/1171874
^ permalink raw reply [flat|nested] 83+ messages in thread
* [olang/patches/.build.yml] build success
2024-03-17 21:29 [PATCH olang v2 3/3] parser: add all binary operation expressions Johnny Richard
@ 2024-03-17 20:37 ` builds.sr.ht
0 siblings, 0 replies; 83+ messages in thread
From: builds.sr.ht @ 2024-03-17 20:37 UTC (permalink / raw)
To: Johnny Richard; +Cc: ~johnnyrichard/olang-devel
olang/patches/.build.yml: SUCCESS in 38s
[frontend: add binary operation expr support][0] v2 from [Johnny Richard][1]
[0]: https://lists.sr.ht/~johnnyrichard/olang-devel/patches/50275
[1]: mailto:johnny@johnnyrichard.com
✓ #1171442 SUCCESS olang/patches/.build.yml https://builds.sr.ht/~johnnyrichard/job/1171442
^ permalink raw reply [flat|nested] 83+ messages in thread
* Re: [olang/patches/.build.yml] build success
2024-03-14 4:29 ` Ricardo Kagawa
@ 2024-03-14 22:43 ` Johnny Richard
0 siblings, 0 replies; 83+ messages in thread
From: Johnny Richard @ 2024-03-14 22:43 UTC (permalink / raw)
To: Ricardo Kagawa; +Cc: ~johnnyrichard/olang-devel
Thank you very much for you contribution, I love it <3.
nitpick for next replies:
1) You've replied to the CI build reply. Next time try to reply to
the right thread.
2) Your message has few weird line breaks. I don't know why it's
happening (noticed you are using Thunderbird). However, you can
make sure your setup is correctly configured to send plain text
emails by visiting this website https://useplaintext.email/
On Thu, Mar 14, 2024 at 01:29:09AM -0300, Ricardo Kagawa wrote:
> >> This grammar adds the token SEMICOLON (';') for every statement. I know
> we
> >> agreed make it optional, but the SEMICOLON makes the parser much more
> >> convenient to implement.
> >>
> >> And this is the first topic I would like to discuss. Let me know if you
> >> agree otherwise I can adapt the grammar to make SEMICOLON optional.
> >
> > (...) Therefore, I'm curious about your statement that using a
> > semicolon makes the parser much more convenient to implement. Could you
> > elaborate on this? Have you encountered any new considerations that might
> > complicate the implementation?
>
> My limited understanding is that the semicolon would indeed be more
> convenient, as it would be a definitive end-of-statement symbol,
> requiring no lookahead to resolve as such. The LF token could be
> ambiguous on its own (between end-of-statement and white space), so
> some lookahead would be required to resolve it.
You are right about it. I had to implement the lookahead capability in
order to skip LF tokens.
> But it should be alright, as long as the language remains context-free.
> Even if it becomes ambiguous, non-deterministic, or requires a long
> lookahead. Ideally it should be determinitstic for linear time
> performance, but it seems there are parsers that can run close to it in
> the average case, as long as the language remains close to
> deterministic.
>
> And I don't have a strong opinion on the semicolon issue, except that
> it must be an option. But whatever we do, we must avoid the following
> pitfall from JavaScript:
>
> ```javascript
> example
> ;(x)
> ```
>
> The semicolon is mandatory here, because otherwise `(x)` is handled as
> an argument list, and `example` would be called as a function. That is,
> it would be a multi-line statement, instead of two separate statements.
>
> And why anyone would do this?
>
> ```javascript
> const x = y.example
> ;(() => {
> console.log(x)
> })()
> ```
I strong agree on avoid those odd JavaScript design. I think we can
continue with optional SEMICOLON. I also think it makes a better
programmer experience.
> >> The grammar was made by using a EBNF evaluator tool[1].
> >>
> >> [1]: https://mdkrajnak.github.io/ebnftest/
> >
> > I would add this link at the markdown, so then people can play with it.
>
> I would make an even stronger argument for including the link in the
> docs. A good language specification also specifies which language
> specification grammar is used for the specification itself. And the
> EBNF in particular is not properly standardized, so you really need to
> specify which EBNF variant you are using.
>
> The link should thus be good enough to refer to the EBNF implementation
> used in this specification, although a permanent (version locked) link
> would be better.
Sure, I can add it to the document. I'm not sure how you want to
version lock this variant. Should I add a specific github/git tag
version to the document?
> As for my revision of the grammar:
I liked all comments and definitely it seems to be better version. In
my option we can start with you changes and keep this document alive for
future discussion. Not sure about Carlos. Let see his thoughts on that
as well.
> Further discussion:
>
> - Is the language going to support Unicode? If so, `<alpha>` could use
> the _L:Letter_ Unicode category instead of being limited to
> `[a-zA-Z]`. But the EBNF tool does not support Unicode categories in
> its regular expressions (it does not support flags). Also don't
> forget to rename it to `<letter>` in that case.
>
> - It would help developers in non-English speaking countries, but it
> could be difficult to work with multi-byte characters and Unicode
> normalization.
I lack knowledge to answer this question right know. I would say to
keep it simple as much as we can on this earlier stage (ASCII only)
unless you have a big concern.
> - There are more linear space and line break characters than the ones
> included here, even within ASCII, although they are not all that
> important. Even more in Unicode (some under _Cc:Other/control_,
> others under _Z:Separator_). Should we support them?
Let's add the remaining ASCII ones meanwhile.
> - The function definition could accept a single expression as an
> alternative to its `<block>`, similar to Kotlin.
Scala also has this capability. But I think it doesn't fit well in our
current function declaration:
fn f(): u32 <statement>
^
If we don't add a token in here like **=** it will be very
weird.
No strong options here to be honest.
> - The integer literal could include optional underline separators for
> readability. Just need to be careful not to start with underline, to
> avoid ambiguity with identifiers.
I like that. We can have it as well.
> - I guess we don't have to support the full set of Unicode digits, since
> we don't know if these digits would even be decimal in the first
> place. The numbering system could be very different from our own, so
> it is likely not feasible to support them.
Perhaps we could postpone the Unicode support?
> - I have not checked if this syntax would avoid that edge case with
> JavaScript I mentioned in the beginning. I might check that next
> time (I'm still not sure of how).
Maybe we are going to discovery it on the implementation process.
> - It might seem strange that I included semantic non-terminals here,
> despite having removed non-terminals for symbols and keywords. I can't
> say for sure, since this is my first time trying this style, but I
> suspect that besides making the language specification easier to
> understand, the important bits to hook into in the parser will be
> around these symbols. That is, it could simplify some work on the
> parser.
ACK
^ permalink raw reply [flat|nested] 83+ messages in thread
* Re: [olang/patches/.build.yml] build success
2024-03-08 23:09 ` [olang/patches/.build.yml] build success builds.sr.ht
@ 2024-03-14 4:29 ` Ricardo Kagawa
2024-03-14 22:43 ` Johnny Richard
0 siblings, 1 reply; 83+ messages in thread
From: Ricardo Kagawa @ 2024-03-14 4:29 UTC (permalink / raw)
To: ~johnnyrichard/olang-devel; +Cc: builds.sr.ht
>> This grammar adds the token SEMICOLON (';') for every statement. I
know we
>> agreed make it optional, but the SEMICOLON makes the parser much more
>> convenient to implement.
>>
>> And this is the first topic I would like to discuss. Let me know if you
>> agree otherwise I can adapt the grammar to make SEMICOLON optional.
>
> (...) Therefore, I'm curious about your statement that using a
> semicolon makes the parser much more convenient to implement. Could you
> elaborate on this? Have you encountered any new considerations that might
> complicate the implementation?
My limited understanding is that the semicolon would indeed be more
convenient, as it would be a definitive end-of-statement symbol,
requiring no lookahead to resolve as such. The LF token could be
ambiguous on its own (between end-of-statement and white space), so
some lookahead would be required to resolve it.
But it should be alright, as long as the language remains context-free.
Even if it becomes ambiguous, non-deterministic, or requires a long
lookahead. Ideally it should be determinitstic for linear time
performance, but it seems there are parsers that can run close to it in
the average case, as long as the language remains close to
deterministic.
And I don't have a strong opinion on the semicolon issue, except that
it must be an option. But whatever we do, we must avoid the following
pitfall from JavaScript:
```javascript
example
;(x)
```
The semicolon is mandatory here, because otherwise `(x)` is handled as
an argument list, and `example` would be called as a function. That is,
it would be a multi-line statement, instead of two separate statements.
And why anyone would do this?
```javascript
const x = y.example
;(() => {
console.log(x)
})()
```
Immediately invoked function expressions are a thing in JavaScript, and
it would not be uncommon to have some expression ending with an
identifier right before them.
>> The grammar was made by using a EBNF evaluator tool[1].
>>
>> [1]: https://mdkrajnak.github.io/ebnftest/
>
> I would add this link at the markdown, so then people can play with it.
I would make an even stronger argument for including the link in the
docs. A good language specification also specifies which language
specification grammar is used for the specification itself. And the
EBNF in particular is not properly standardized, so you really need to
specify which EBNF variant you are using.
The link should thus be good enough to refer to the EBNF implementation
used in this specification, although a permanent (version locked) link
would be better.
----
As for my revision of the grammar:
- Separated rules into sections.
- Added optional white space around the program.
- You don't actually need non-terminal symbols for keywords. Especially
if you are including the keyword in the symbol name.
- You don't need non-terminal symbols for symbols either, unless you
have a more "semantic" name for it. There should not be another
"semicolon" besides `;`, for example.
- In Johnny's version the function name is a single identifier. I don't
know why Carlos's version made it multiple. I have made it single
again.
- In Johnny's version the space before the return type is optional. I
don't know why Carlos's version made it mandatory. I have made it
optional again.
- Replaced `<identifier>` in `<function-definition>` with
`<function-name>` to express that this identifier is the name of the
declared function. Then, `<function-name>` is just `<identifier>`.
- Renamed `<fn-args>` to `<function-parameters>`, since parameters are
the variables in a function declaration, while arguments are the
values bound to those variables during function calls.
- Replaced `<type>` for `<return-type>` in `<function-declaration>` to
express that this type identifier is the return type of the function.
Then, `<return-type>` is just `<type>`.
- Replaced `<block>` in `<function-definition>` for `<function-body>` to
express that this block is the body of the declared function.
- Reworked `<block>`, `<statement>` and `<end-of-statement>` to allow
for:
- Single statement followd by optional end-of-statement;
- Statement list with mandatory end-of-statement between statements;
- But the statements could be made optional, yet I did not in this
version, as there is no `void` return type, currently.
- Replaced `<number>` in `<return-statement>` with `<expression>` to
prepare for them in the future. The only allowed expression is still
an integer literal, though.
- Renamed `<number>` to `<integer>`, and reworked it to actually
represent decimal integer literals. Sequences of zero digits are now
forbidden at the left side, but a lone zero digit is still allowed.
- Reworked `<identifier>` to better express that it starts with
`<alpha>` or underline, followed by zero or more `<alpha>`, `<digit>`
or underline.
- Removed `_` from `<alpha>` to better reflect the name (as underline is
not an alphabetic character).
- Renamed `<space>` for `<ws>` to avoid ambiguity with the character
U+0020 Space, and made it a one-or-more list. Also introduced `<ows>`
for "optional white space". Shorter names were preferred here due to
these symbols in particular being used very frequently.
- Also introduced `<line-break>` as either LF, CR or CRLF. Otherwise the
CRLF sequence would be parsed as two separate line breaks. Not that it
would matter that much, except maybe for mapping line numbers.
```
(* Entry Point *)
<program> ::= <ows> <function-definition> <ows>
(* Functions *)
<function-definition> ::= 'fn' <ws> <function-name> <ows>
<function-parameters> <ows> ':' <ows> <return-type> <ows> <function-body>
<function-name> ::= <identifier>
<function-parameters> ::= '(' <ows> ')'
<return-type> ::= <type>
<function-body> ::= <block>
(* Statements *)
<block> ::= '{' <ows> <statement> <ows>
(<end-of-statement> <ows> <statement> <ows>)* <end-of-statement>? <ows> '}'
<end-of-statement> ::= ';' | <line-break>
<statement> ::= <return-statement>
<return-statement> ::= 'return' <ws> <expression>
(* Expressions *)
<expression> ::= <integer>
(* Identifiers *)
<type> ::= 'u32'
<identifier> ::= (<alpha> | '_') (<alpha> | <digit> | '_')*
(* Literals *)
<integer> ::= <integer-base10>
<integer-base10> ::= #'[1-9]' <digit>* | '0'
(* Utilities *)
<ws> ::= <white-space>+
<ows> ::= <white-space>*
<white-space> ::= <linear-space> | <line-break>
<line-break> ::= '\n' | '\r' | '\r\n'
<linear-space> ::= #'[ \t]'
<alpha> ::= #'[a-zA-Z]'
<digit> ::= #'[0-9]'
```
Further discussion:
- Is the language going to support Unicode? If so, `<alpha>` could use
the _L:Letter_ Unicode category instead of being limited to
`[a-zA-Z]`. But the EBNF tool does not support Unicode categories in
its regular expressions (it does not support flags). Also don't
forget to rename it to `<letter>` in that case.
- It would help developers in non-English speaking countries, but it
could be difficult to work with multi-byte characters and Unicode
normalization.
- There are more linear space and line break characters than the ones
included here, even within ASCII, although they are not all that
important. Even more in Unicode (some under _Cc:Other/control_,
others under _Z:Separator_). Should we support them?
- The function definition could accept a single expression as an
alternative to its `<block>`, similar to Kotlin.
- The integer literal could include optional underline separators for
readability. Just need to be careful not to start with underline, to
avoid ambiguity with identifiers.
- I guess we don't have to support the full set of Unicode digits, since
we don't know if these digits would even be decimal in the first
place. The numbering system could be very different from our own, so
it is likely not feasible to support them.
- I have not checked if this syntax would avoid that edge case with
JavaScript I mentioned in the beginning. I might check that next
time (I'm still not sure of how).
- It might seem strange that I included semantic non-terminals here,
despite having removed non-terminals for symbols and keywords. I can't
say for sure, since this is my first time trying this style, but I
suspect that besides making the language specification easier to
understand, the important bits to hook into in the parser will be
around these symbols. That is, it could simplify some work on the
parser.
^ permalink raw reply [flat|nested] 83+ messages in thread
* [olang/patches/.build.yml] build success
2024-03-13 21:21 [PATCH olang v1 3/3] parser: add basic arithmetic expressions '+' '*' '/' '-' Johnny Richard
@ 2024-03-13 20:29 ` builds.sr.ht
0 siblings, 0 replies; 83+ messages in thread
From: builds.sr.ht @ 2024-03-13 20:29 UTC (permalink / raw)
To: Johnny Richard; +Cc: ~johnnyrichard/olang-devel
olang/patches/.build.yml: SUCCESS in 34s
[frontend: add basic arithmetic expr support][0] from [Johnny Richard][1]
[0]: https://lists.sr.ht/~johnnyrichard/olang-devel/patches/50195
[1]: mailto:johnny@johnnyrichard.com
✓ #1168244 SUCCESS olang/patches/.build.yml https://builds.sr.ht/~johnnyrichard/job/1168244
^ permalink raw reply [flat|nested] 83+ messages in thread
* [olang/patches/.build.yml] build success
2024-03-13 12:44 [PATCH olang v3] refactor: rename zero programming language to olang Fabio Maciel
@ 2024-03-13 12:45 ` builds.sr.ht
0 siblings, 0 replies; 83+ messages in thread
From: builds.sr.ht @ 2024-03-13 12:45 UTC (permalink / raw)
To: Fabio Maciel; +Cc: ~johnnyrichard/olang-devel
olang/patches/.build.yml: SUCCESS in 35s
[refactor: rename zero programming language to olang][0] v3 from [Fabio Maciel][1]
[0]: https://lists.sr.ht/~johnnyrichard/olang-devel/patches/50188
[1]: mailto:fabio@fabiomaciel.com
✓ #1167864 SUCCESS olang/patches/.build.yml https://builds.sr.ht/~johnnyrichard/job/1167864
^ permalink raw reply [flat|nested] 83+ messages in thread
* [olang/patches/.build.yml] build success
2024-03-12 19:35 [PATCH olang v1] refactor: rename zero programming language to olang Johnny Richard
@ 2024-03-12 18:40 ` builds.sr.ht
0 siblings, 0 replies; 83+ messages in thread
From: builds.sr.ht @ 2024-03-12 18:40 UTC (permalink / raw)
To: Johnny Richard; +Cc: ~johnnyrichard/olang-devel
olang/patches/.build.yml: SUCCESS in 36s
[refactor: rename zero programming language to olang][0] from [Johnny Richard][1]
[0]: https://lists.sr.ht/~johnnyrichard/olang-devel/patches/50167
[1]: mailto:johnny@johnnyrichard.com
✓ #1167072 SUCCESS olang/patches/.build.yml https://builds.sr.ht/~johnnyrichard/job/1167072
^ permalink raw reply [flat|nested] 83+ messages in thread
* [olang/patches/.build.yml] build success
2024-03-11 8:48 [PATCH olang] site: change dns to o-lang.org Johnny Richard
@ 2024-03-11 7:50 ` builds.sr.ht
0 siblings, 0 replies; 83+ messages in thread
From: builds.sr.ht @ 2024-03-11 7:50 UTC (permalink / raw)
To: Johnny Richard; +Cc: ~johnnyrichard/olang-devel
olang/patches/.build.yml: SUCCESS in 34s
[site: change dns to o-lang.org][0] from [Johnny Richard][1]
[0]: https://lists.sr.ht/~johnnyrichard/olang-devel/patches/50131
[1]: mailto:johnny@johnnyrichard.com
✓ #1166160 SUCCESS olang/patches/.build.yml https://builds.sr.ht/~johnnyrichard/job/1166160
^ permalink raw reply [flat|nested] 83+ messages in thread
* [olang/patches/.build.yml] build success
2024-03-09 0:05 [RFC PATCH olang v1] docs: create zero programming language specification Johnny Richard
@ 2024-03-08 23:09 ` builds.sr.ht
2024-03-14 4:29 ` Ricardo Kagawa
0 siblings, 1 reply; 83+ messages in thread
From: builds.sr.ht @ 2024-03-08 23:09 UTC (permalink / raw)
To: Johnny Richard; +Cc: ~johnnyrichard/olang-devel
olang/patches/.build.yml: SUCCESS in 33s
[docs: create zero programming language specification][0] from [Johnny Richard][1]
[0]: https://lists.sr.ht/~johnnyrichard/olang-devel/patches/50092
[1]: mailto:johnny@johnnyrichard.com
✓ #1164786 SUCCESS olang/patches/.build.yml https://builds.sr.ht/~johnnyrichard/job/1164786
^ permalink raw reply [flat|nested] 83+ messages in thread
* [olang/patches/.build.yml] build success
2024-03-08 22:39 [PATCH olang v2 3/3] tests: add tests for the minimal possible olang program Carlos Maniero
@ 2024-03-08 22:40 ` builds.sr.ht
0 siblings, 0 replies; 83+ messages in thread
From: builds.sr.ht @ 2024-03-08 22:40 UTC (permalink / raw)
To: Carlos Maniero; +Cc: ~johnnyrichard/olang-devel
olang/patches/.build.yml: SUCCESS in 33s
[test: cli: cover compilation pipeline][0] v2 from [Carlos Maniero][1]
[0]: https://lists.sr.ht/~johnnyrichard/olang-devel/patches/50091
[1]: mailto:carlos@maniero.me
✓ #1164772 SUCCESS olang/patches/.build.yml https://builds.sr.ht/~johnnyrichard/job/1164772
^ permalink raw reply [flat|nested] 83+ messages in thread
* [olang/patches/.build.yml] build success
2024-03-08 23:13 [PATCH olang v1] ast: add ast_node root for the entire program Johnny Richard
@ 2024-03-08 22:13 ` builds.sr.ht
0 siblings, 0 replies; 83+ messages in thread
From: builds.sr.ht @ 2024-03-08 22:13 UTC (permalink / raw)
To: Johnny Richard; +Cc: ~johnnyrichard/olang-devel
olang/patches/.build.yml: SUCCESS in 33s
[ast: add ast_node root for the entire program][0] from [Johnny Richard][1]
[0]: https://lists.sr.ht/~johnnyrichard/olang-devel/patches/50090
[1]: mailto:johnny@johnnyrichard.com
✓ #1164762 SUCCESS olang/patches/.build.yml https://builds.sr.ht/~johnnyrichard/job/1164762
^ permalink raw reply [flat|nested] 83+ messages in thread
* [olang/patches/.build.yml] build success
2024-03-07 23:23 [PATCH olang 3/3] tests: add tests for the minimal possible olang program Carlos Maniero
@ 2024-03-07 23:24 ` builds.sr.ht
0 siblings, 0 replies; 83+ messages in thread
From: builds.sr.ht @ 2024-03-07 23:24 UTC (permalink / raw)
To: Carlos Maniero; +Cc: ~johnnyrichard/olang-devel
olang/patches/.build.yml: SUCCESS in 34s
[tests: cli: cover compilation pipeline][0] from [Carlos Maniero][1]
[0]: https://lists.sr.ht/~johnnyrichard/olang-devel/patches/50070
[1]: mailto:carlos@maniero.me
✓ #1164273 SUCCESS olang/patches/.build.yml https://builds.sr.ht/~johnnyrichard/job/1164273
^ permalink raw reply [flat|nested] 83+ messages in thread
* [olang/patches/.build.yml] build success
2024-03-01 22:24 [PATCH olang v2 4/4] parser: create simplified parser for tiny AST Johnny Richard
@ 2024-03-01 21:32 ` builds.sr.ht
0 siblings, 0 replies; 83+ messages in thread
From: builds.sr.ht @ 2024-03-01 21:32 UTC (permalink / raw)
To: Johnny Richard; +Cc: ~johnnyrichard/olang-devel
olang/patches/.build.yml: SUCCESS in 42s
[create initial syntax analysis logic][0] v2 from [Johnny Richard][1]
[0]: https://lists.sr.ht/~johnnyrichard/olang-devel/patches/49932
[1]: mailto:johnny@johnnyrichard.com
✓ #1160326 SUCCESS olang/patches/.build.yml https://builds.sr.ht/~johnnyrichard/job/1160326
^ permalink raw reply [flat|nested] 83+ messages in thread
* [olang/patches/.build.yml] build success
2024-02-28 19:04 [PATCH olang v1 4/4] parser: create simplified parser for tiny AST Johnny Richard
@ 2024-02-28 18:11 ` builds.sr.ht
0 siblings, 0 replies; 83+ messages in thread
From: builds.sr.ht @ 2024-02-28 18:11 UTC (permalink / raw)
To: Johnny Richard; +Cc: ~johnnyrichard/olang-devel
olang/patches/.build.yml: SUCCESS in 49s
[create initial syntax analysis logic][0] from [Johnny Richard][1]
[0]: https://lists.sr.ht/~johnnyrichard/olang-devel/patches/49873
[1]: mailto:johnny@johnnyrichard.com
✓ #1159030 SUCCESS olang/patches/.build.yml https://builds.sr.ht/~johnnyrichard/job/1159030
^ permalink raw reply [flat|nested] 83+ messages in thread
* [olang/patches/.build.yml] build success
2024-02-28 14:25 [PATCH olang v3] arena: optimization: ensure alignment memory access Carlos Maniero
@ 2024-02-28 14:26 ` builds.sr.ht
0 siblings, 0 replies; 83+ messages in thread
From: builds.sr.ht @ 2024-02-28 14:26 UTC (permalink / raw)
To: Carlos Maniero; +Cc: ~johnnyrichard/olang-devel
olang/patches/.build.yml: SUCCESS in 44s
[arena: optimization: ensure alignment memory access][0] v3 from [Carlos Maniero][1]
[0]: https://lists.sr.ht/~johnnyrichard/olang-devel/patches/49869
[1]: mailto:carlos@maniero.me
✓ #1158813 SUCCESS olang/patches/.build.yml https://builds.sr.ht/~johnnyrichard/job/1158813
^ permalink raw reply [flat|nested] 83+ messages in thread
* [olang/patches/.build.yml] build success
2024-02-28 12:37 [PATCH olang v2] cli: replace memory allocation malloc -> arena Johnny Richard
@ 2024-02-28 11:39 ` builds.sr.ht
0 siblings, 0 replies; 83+ messages in thread
From: builds.sr.ht @ 2024-02-28 11:39 UTC (permalink / raw)
To: Johnny Richard; +Cc: ~johnnyrichard/olang-devel
olang/patches/.build.yml: SUCCESS in 45s
[cli: replace memory allocation malloc -> arena][0] v2 from [Johnny Richard][1]
[0]: https://lists.sr.ht/~johnnyrichard/olang-devel/patches/49866
[1]: mailto:johnny@johnnyrichard.com
✓ #1158692 SUCCESS olang/patches/.build.yml https://builds.sr.ht/~johnnyrichard/job/1158692
^ permalink raw reply [flat|nested] 83+ messages in thread
* [olang/patches/.build.yml] build success
2024-02-27 19:59 [PATCH olang v2 2/2] utils: create hash map data structure Johnny Richard
@ 2024-02-27 19:01 ` builds.sr.ht
0 siblings, 0 replies; 83+ messages in thread
From: builds.sr.ht @ 2024-02-27 19:01 UTC (permalink / raw)
To: Johnny Richard; +Cc: ~johnnyrichard/olang-devel
olang/patches/.build.yml: SUCCESS in 37s
[introduce hash map data structure][0] v2 from [Johnny Richard][1]
[0]: https://lists.sr.ht/~johnnyrichard/olang-devel/patches/49853
[1]: mailto:johnny@johnnyrichard.com
✓ #1158194 SUCCESS olang/patches/.build.yml https://builds.sr.ht/~johnnyrichard/job/1158194
^ permalink raw reply [flat|nested] 83+ messages in thread
* [olang/patches/.build.yml] build success
2024-02-24 20:40 [PATCH olang] test: fix suite name for list_test and arena_test Johnny Richard
@ 2024-02-24 19:42 ` builds.sr.ht
0 siblings, 0 replies; 83+ messages in thread
From: builds.sr.ht @ 2024-02-24 19:42 UTC (permalink / raw)
To: Johnny Richard; +Cc: ~johnnyrichard/olang-devel
olang/patches/.build.yml: SUCCESS in 32s
[test: fix suite name for list_test and arena_test][0] from [Johnny Richard][1]
[0]: https://lists.sr.ht/~johnnyrichard/olang-devel/patches/49779
[1]: mailto:johnny@johnnyrichard.com
✓ #1156769 SUCCESS olang/patches/.build.yml https://builds.sr.ht/~johnnyrichard/job/1156769
^ permalink raw reply [flat|nested] 83+ messages in thread
* [olang/patches/.build.yml] build success
2024-02-22 19:09 [PATCH olang] cli: replace memory allocation malloc -> arena Johnny Richard
@ 2024-02-22 18:11 ` builds.sr.ht
0 siblings, 0 replies; 83+ messages in thread
From: builds.sr.ht @ 2024-02-22 18:11 UTC (permalink / raw)
To: Johnny Richard; +Cc: ~johnnyrichard/olang-devel
olang/patches/.build.yml: SUCCESS in 37s
[cli: replace memory allocation malloc -> arena][0] from [Johnny Richard][1]
[0]: https://lists.sr.ht/~johnnyrichard/olang-devel/patches/49749
[1]: mailto:johnny@johnnyrichard.com
✓ #1155615 SUCCESS olang/patches/.build.yml https://builds.sr.ht/~johnnyrichard/job/1155615
^ permalink raw reply [flat|nested] 83+ messages in thread
* [olang/patches/.build.yml] build success
2024-02-22 18:38 [PATCH olang] docs: add DCO information on hacking page Johnny Richard
@ 2024-02-22 17:41 ` builds.sr.ht
0 siblings, 0 replies; 83+ messages in thread
From: builds.sr.ht @ 2024-02-22 17:41 UTC (permalink / raw)
To: Johnny Richard; +Cc: ~johnnyrichard/olang-devel
olang/patches/.build.yml: SUCCESS in 37s
[docs: add DCO information on hacking page][0] from [Johnny Richard][1]
[0]: https://lists.sr.ht/~johnnyrichard/olang-devel/patches/49746
[1]: mailto:johnny@johnnyrichard.com
✓ #1155599 SUCCESS olang/patches/.build.yml https://builds.sr.ht/~johnnyrichard/job/1155599
^ permalink raw reply [flat|nested] 83+ messages in thread
* [olang/patches/.build.yml] build success
2024-02-22 18:24 [PATCH olang] build: rename 0c.c file to main.c Johnny Richard
@ 2024-02-22 17:26 ` builds.sr.ht
0 siblings, 0 replies; 83+ messages in thread
From: builds.sr.ht @ 2024-02-22 17:26 UTC (permalink / raw)
To: Johnny Richard; +Cc: ~johnnyrichard/olang-devel
olang/patches/.build.yml: SUCCESS in 37s
[build: rename 0c.c file to main.c][0] from [Johnny Richard][1]
[0]: https://lists.sr.ht/~johnnyrichard/olang-devel/patches/49745
[1]: mailto:johnny@johnnyrichard.com
✓ #1155591 SUCCESS olang/patches/.build.yml https://builds.sr.ht/~johnnyrichard/job/1155591
^ permalink raw reply [flat|nested] 83+ messages in thread
* [olang/patches/.build.yml] build success
2024-02-21 22:20 [PATCH olang 2/2] utils: create hash map data structure Johnny Richard
@ 2024-02-21 21:24 ` builds.sr.ht
0 siblings, 0 replies; 83+ messages in thread
From: builds.sr.ht @ 2024-02-21 21:24 UTC (permalink / raw)
To: Johnny Richard; +Cc: ~johnnyrichard/olang-devel
olang/patches/.build.yml: SUCCESS in 44s
[introduce hash map data structure][0] from [Johnny Richard][1]
[0]: https://lists.sr.ht/~johnnyrichard/olang-devel/patches/49732
[1]: mailto:johnny@johnnyrichard.com
✓ #1155192 SUCCESS olang/patches/.build.yml https://builds.sr.ht/~johnnyrichard/job/1155192
^ permalink raw reply [flat|nested] 83+ messages in thread
* [olang/patches/.build.yml] build success
2024-02-21 15:09 [PATCH olang v2] arena: optimization: make arena 8 bits aligned Carlos Maniero
@ 2024-02-21 15:09 ` builds.sr.ht
0 siblings, 0 replies; 83+ messages in thread
From: builds.sr.ht @ 2024-02-21 15:09 UTC (permalink / raw)
To: Carlos Maniero; +Cc: ~johnnyrichard/olang-devel
olang/patches/.build.yml: SUCCESS in 33s
[arena: optimization: make arena 8 bits aligned][0] v2 from [Carlos Maniero][1]
[0]: https://lists.sr.ht/~johnnyrichard/olang-devel/patches/49723
[1]: mailto:carlos@maniero.me
✓ #1154947 SUCCESS olang/patches/.build.yml https://builds.sr.ht/~johnnyrichard/job/1154947
^ permalink raw reply [flat|nested] 83+ messages in thread
* [olang/patches/.build.yml] build success
2024-02-21 5:52 [PATCH olang] arena: optimization: make arena 8 bits aligned Carlos Maniero
@ 2024-02-21 5:53 ` builds.sr.ht
0 siblings, 0 replies; 83+ messages in thread
From: builds.sr.ht @ 2024-02-21 5:53 UTC (permalink / raw)
To: Carlos Maniero; +Cc: ~johnnyrichard/olang-devel
olang/patches/.build.yml: SUCCESS in 35s
[arena: optimization: make arena 8 bits aligned][0] from [Carlos Maniero][1]
[0]: https://lists.sr.ht/~johnnyrichard/olang-devel/patches/49718
[1]: mailto:carlos@maniero.me
✓ #1154549 SUCCESS olang/patches/.build.yml https://builds.sr.ht/~johnnyrichard/job/1154549
^ permalink raw reply [flat|nested] 83+ messages in thread
* [olang/patches/.build.yml] build success
2024-02-20 23:37 [PATCH olang] utils: add linked-list Carlos Maniero
@ 2024-02-20 23:37 ` builds.sr.ht
0 siblings, 0 replies; 83+ messages in thread
From: builds.sr.ht @ 2024-02-20 23:37 UTC (permalink / raw)
To: Carlos Maniero; +Cc: ~johnnyrichard/olang-devel
olang/patches/.build.yml: SUCCESS in 35s
[utils: add linked-list][0] from [Carlos Maniero][1]
[0]: https://lists.sr.ht/~johnnyrichard/olang-devel/patches/49714
[1]: mailto:carlos@maniero.me
✓ #1154366 SUCCESS olang/patches/.build.yml https://builds.sr.ht/~johnnyrichard/job/1154366
^ permalink raw reply [flat|nested] 83+ messages in thread
* [olang/patches/.build.yml] build success
2024-02-20 17:35 [PATCH olang v3] utils: add arena Carlos Maniero
@ 2024-02-20 17:41 ` builds.sr.ht
0 siblings, 0 replies; 83+ messages in thread
From: builds.sr.ht @ 2024-02-20 17:41 UTC (permalink / raw)
To: Carlos Maniero; +Cc: ~johnnyrichard/olang-devel
olang/patches/.build.yml: SUCCESS in 33s
[utils: add arena][0] v3 from [Carlos Maniero][1]
[0]: https://lists.sr.ht/~johnnyrichard/olang-devel/patches/49711
[1]: mailto:carlos@maniero.me
✓ #1154191 SUCCESS olang/patches/.build.yml https://builds.sr.ht/~johnnyrichard/job/1154191
^ permalink raw reply [flat|nested] 83+ messages in thread
* [olang/patches/.build.yml] build success
2024-02-19 20:42 [PATCH olang v5 4/4] lexer: test: add integration tests for --dump-tokens Carlos Maniero
@ 2024-02-19 20:48 ` builds.sr.ht
0 siblings, 0 replies; 83+ messages in thread
From: builds.sr.ht @ 2024-02-19 20:48 UTC (permalink / raw)
To: Carlos Maniero; +Cc: ~johnnyrichard/olang-devel
olang/patches/.build.yml: SUCCESS in 34s
[Create --dump-tokens on compiler cli][0] v5 from [Carlos Maniero][1]
[0]: https://lists.sr.ht/~johnnyrichard/olang-devel/patches/49685
[1]: mailto:carlos@maniero.me
✓ #1153651 SUCCESS olang/patches/.build.yml https://builds.sr.ht/~johnnyrichard/job/1153651
^ permalink raw reply [flat|nested] 83+ messages in thread
* [olang/patches/.build.yml] build success
2024-02-19 1:44 [PATCH olang v3 2/2] lexer: create --dump-tokens cli command Johnny Richard
@ 2024-02-19 0:47 ` builds.sr.ht
0 siblings, 0 replies; 83+ messages in thread
From: builds.sr.ht @ 2024-02-19 0:47 UTC (permalink / raw)
To: Johnny Richard; +Cc: ~johnnyrichard/olang-devel
olang/patches/.build.yml: SUCCESS in 34s
[Create --dump-tokens on compiler cli][0] v3 from [Johnny Richard][1]
[0]: https://lists.sr.ht/~johnnyrichard/olang-devel/patches/49645
[1]: mailto:johnny@johnnyrichard.com
✓ #1153060 SUCCESS olang/patches/.build.yml https://builds.sr.ht/~johnnyrichard/job/1153060
^ permalink raw reply [flat|nested] 83+ messages in thread
* [olang/patches/.build.yml] build success
2024-02-18 0:50 [PATCH olang 2/2] tests: add unit tests configuration Carlos Maniero
@ 2024-02-18 0:55 ` builds.sr.ht
0 siblings, 0 replies; 83+ messages in thread
From: builds.sr.ht @ 2024-02-18 0:55 UTC (permalink / raw)
To: Carlos Maniero; +Cc: ~johnnyrichard/olang-devel
olang/patches/.build.yml: SUCCESS in 33s
[add unit tests config][0] from [Carlos Maniero][1]
[0]: https://lists.sr.ht/~johnnyrichard/olang-devel/patches/49618
[1]: mailto:carlos@maniero.me
✓ #1152377 SUCCESS olang/patches/.build.yml https://builds.sr.ht/~johnnyrichard/job/1152377
^ permalink raw reply [flat|nested] 83+ messages in thread
* [olang/patches/.build.yml] build success
2024-02-17 20:12 [PATCH olang] docs: add mobile version Carlos Maniero
@ 2024-02-17 20:17 ` builds.sr.ht
0 siblings, 0 replies; 83+ messages in thread
From: builds.sr.ht @ 2024-02-17 20:17 UTC (permalink / raw)
To: Carlos Maniero; +Cc: ~johnnyrichard/olang-devel
olang/patches/.build.yml: SUCCESS in 31s
[docs: add mobile version][0] from [Carlos Maniero][1]
[0]: https://lists.sr.ht/~johnnyrichard/olang-devel/patches/49612
[1]: mailto:carlos@maniero.me
✓ #1152244 SUCCESS olang/patches/.build.yml https://builds.sr.ht/~johnnyrichard/job/1152244
^ permalink raw reply [flat|nested] 83+ messages in thread
* [olang/patches/.build.yml] build success
2024-02-17 21:04 [PATCH olang] docs: deploy: replace shrt.site domain by olang.johnnyrichard.com Johnny Richard
@ 2024-02-17 20:03 ` builds.sr.ht
0 siblings, 0 replies; 83+ messages in thread
From: builds.sr.ht @ 2024-02-17 20:03 UTC (permalink / raw)
To: Johnny Richard; +Cc: ~johnnyrichard/olang-devel
olang/patches/.build.yml: SUCCESS in 31s
[docs: deploy: replace shrt.site domain by olang.johnnyrichard.com][0] from [Johnny Richard][1]
[0]: https://lists.sr.ht/~johnnyrichard/olang-devel/patches/49611
[1]: mailto:johnny@johnnyrichard.com
✓ #1152239 SUCCESS olang/patches/.build.yml https://builds.sr.ht/~johnnyrichard/job/1152239
^ permalink raw reply [flat|nested] 83+ messages in thread
* [olang/patches/.build.yml] build success
2024-02-17 20:38 [PATCH olang] docs: build: fix docs publishing task Johnny Richard
@ 2024-02-17 19:37 ` builds.sr.ht
0 siblings, 0 replies; 83+ messages in thread
From: builds.sr.ht @ 2024-02-17 19:37 UTC (permalink / raw)
To: Johnny Richard; +Cc: ~johnnyrichard/olang-devel
olang/patches/.build.yml: SUCCESS in 31s
[docs: build: fix docs publishing task][0] from [Johnny Richard][1]
[0]: https://lists.sr.ht/~johnnyrichard/olang-devel/patches/49609
[1]: mailto:johnny@johnnyrichard.com
✓ #1152215 SUCCESS olang/patches/.build.yml https://builds.sr.ht/~johnnyrichard/job/1152215
^ permalink raw reply [flat|nested] 83+ messages in thread
* [olang/patches/.build.yml] build success
2024-02-17 18:40 [PATCH olang v2] docs: add HACKING documentation Carlos Maniero
@ 2024-02-17 18:45 ` builds.sr.ht
0 siblings, 0 replies; 83+ messages in thread
From: builds.sr.ht @ 2024-02-17 18:45 UTC (permalink / raw)
To: Carlos Maniero; +Cc: ~johnnyrichard/olang-devel
olang/patches/.build.yml: SUCCESS in 16s
[docs: add HACKING documentation][0] v2 from [Carlos Maniero][1]
[0]: https://lists.sr.ht/~johnnyrichard/olang-devel/patches/49605
[1]: mailto:carlos@maniero.me
✓ #1152165 SUCCESS olang/patches/.build.yml https://builds.sr.ht/~johnnyrichard/job/1152165
^ permalink raw reply [flat|nested] 83+ messages in thread
* [olang/patches/.build.yml] build success
2024-02-17 18:29 [PATCH olang v2] docs: add white mode support Carlos Maniero
@ 2024-02-17 18:34 ` builds.sr.ht
0 siblings, 0 replies; 83+ messages in thread
From: builds.sr.ht @ 2024-02-17 18:34 UTC (permalink / raw)
To: Carlos Maniero; +Cc: ~johnnyrichard/olang-devel
olang/patches/.build.yml: SUCCESS in 17s
[docs: add white mode support][0] v2 from [Carlos Maniero][1]
[0]: https://lists.sr.ht/~johnnyrichard/olang-devel/patches/49604
[1]: mailto:carlos@maniero.me
✓ #1152150 SUCCESS olang/patches/.build.yml https://builds.sr.ht/~johnnyrichard/job/1152150
^ permalink raw reply [flat|nested] 83+ messages in thread
* [olang/patches/.build.yml] build success
2024-02-17 17:46 [PATCH olang] docs: add white-mode support Carlos Maniero
@ 2024-02-17 17:51 ` builds.sr.ht
0 siblings, 0 replies; 83+ messages in thread
From: builds.sr.ht @ 2024-02-17 17:51 UTC (permalink / raw)
To: Carlos Maniero; +Cc: ~johnnyrichard/olang-devel
olang/patches/.build.yml: SUCCESS in 17s
[docs: add white-mode support][0] from [Carlos Maniero][1]
[0]: https://lists.sr.ht/~johnnyrichard/olang-devel/patches/49603
[1]: mailto:carlos@maniero.me
✓ #1152135 SUCCESS olang/patches/.build.yml https://builds.sr.ht/~johnnyrichard/job/1152135
^ permalink raw reply [flat|nested] 83+ messages in thread
* [olang/patches/.build.yml] build success
2024-02-17 16:22 [PATCH olang] docs: add pandoc Carlos Maniero
@ 2024-02-17 16:27 ` builds.sr.ht
0 siblings, 0 replies; 83+ messages in thread
From: builds.sr.ht @ 2024-02-17 16:27 UTC (permalink / raw)
To: Carlos Maniero; +Cc: ~johnnyrichard/olang-devel
olang/patches/.build.yml: SUCCESS in 17s
[docs: add pandoc][0] from [Carlos Maniero][1]
[0]: https://lists.sr.ht/~johnnyrichard/olang-devel/patches/49600
[1]: mailto:carlos@maniero.me
✓ #1152071 SUCCESS olang/patches/.build.yml https://builds.sr.ht/~johnnyrichard/job/1152071
^ permalink raw reply [flat|nested] 83+ messages in thread
* [olang/patches/.build.yml] build success
2024-02-16 16:23 [PATCH olang] docs: build: add deployment script Carlos Maniero
@ 2024-02-16 16:28 ` builds.sr.ht
0 siblings, 0 replies; 83+ messages in thread
From: builds.sr.ht @ 2024-02-16 16:28 UTC (permalink / raw)
To: Carlos Maniero; +Cc: ~johnnyrichard/olang-devel
olang/patches/.build.yml: SUCCESS in 16s
[docs: build: add deployment script][0] from [Carlos Maniero][1]
[0]: https://lists.sr.ht/~johnnyrichard/olang-devel/patches/49578
[1]: mailto:carlos@maniero.me
✓ #1151433 SUCCESS olang/patches/.build.yml https://builds.sr.ht/~johnnyrichard/job/1151433
^ permalink raw reply [flat|nested] 83+ messages in thread
* [olang/patches/.build.yml] build success
2024-02-16 16:24 [PATCH olang v2] docs: add sphinx documentation support Johnny Richard
@ 2024-02-16 15:26 ` builds.sr.ht
0 siblings, 0 replies; 83+ messages in thread
From: builds.sr.ht @ 2024-02-16 15:26 UTC (permalink / raw)
To: Johnny Richard; +Cc: ~johnnyrichard/olang-devel
olang/patches/.build.yml: SUCCESS in 17s
[docs: add sphinx documentation support][0] v2 from [Johnny Richard][1]
[0]: https://lists.sr.ht/~johnnyrichard/olang-devel/patches/49575
[1]: mailto:johnny@johnnyrichard.com
✓ #1151403 SUCCESS olang/patches/.build.yml https://builds.sr.ht/~johnnyrichard/job/1151403
^ permalink raw reply [flat|nested] 83+ messages in thread
* [olang/patches/.build.yml] build success
2024-02-16 8:59 [PATCH olang] docs: add sphinx documentation support Johnny Richard
@ 2024-02-16 8:01 ` builds.sr.ht
0 siblings, 0 replies; 83+ messages in thread
From: builds.sr.ht @ 2024-02-16 8:01 UTC (permalink / raw)
To: Johnny Richard; +Cc: ~johnnyrichard/olang-devel
olang/patches/.build.yml: SUCCESS in 16s
[docs: add sphinx documentation support][0] from [Johnny Richard][1]
[0]: https://lists.sr.ht/~johnnyrichard/olang-devel/patches/49563
[1]: mailto:johnny@johnnyrichard.com
✓ #1151185 SUCCESS olang/patches/.build.yml https://builds.sr.ht/~johnnyrichard/job/1151185
^ permalink raw reply [flat|nested] 83+ messages in thread
* [olang/patches/.build.yml] build success
2024-02-16 3:07 [PATCH olang v3 2/2] tests: add integration test setup Carlos Maniero
@ 2024-02-16 3:12 ` builds.sr.ht
0 siblings, 0 replies; 83+ messages in thread
From: builds.sr.ht @ 2024-02-16 3:12 UTC (permalink / raw)
To: Carlos Maniero; +Cc: ~johnnyrichard/olang-devel
olang/patches/.build.yml: SUCCESS in 15s
[add integration test][0] v3 from [Carlos Maniero][1]
[0]: https://lists.sr.ht/~johnnyrichard/olang-devel/patches/49557
[1]: mailto:carlos@maniero.me
✓ #1151093 SUCCESS olang/patches/.build.yml https://builds.sr.ht/~johnnyrichard/job/1151093
^ permalink raw reply [flat|nested] 83+ messages in thread
* [olang/patches/.build.yml] build success
2024-02-15 16:21 [PATCH olang 2/2] tests: add integration test setup Carlos Maniero
@ 2024-02-15 16:27 ` builds.sr.ht
0 siblings, 0 replies; 83+ messages in thread
From: builds.sr.ht @ 2024-02-15 16:27 UTC (permalink / raw)
To: Carlos Maniero; +Cc: ~johnnyrichard/olang-devel
olang/patches/.build.yml: SUCCESS in 17s
[Add integration tests][0] from [Carlos Maniero][1]
[0]: https://lists.sr.ht/~johnnyrichard/olang-devel/patches/49542
[1]: mailto:carlos@maniero.me
✓ #1150776 SUCCESS olang/patches/.build.yml https://builds.sr.ht/~johnnyrichard/job/1150776
^ permalink raw reply [flat|nested] 83+ messages in thread
* [olang/patches/.build.yml] build success
2024-02-13 20:55 [PATCH olang] docs: fix git send-email config instruction Carlos Maniero
@ 2024-02-13 21:00 ` builds.sr.ht
0 siblings, 0 replies; 83+ messages in thread
From: builds.sr.ht @ 2024-02-13 21:00 UTC (permalink / raw)
To: Carlos Maniero; +Cc: ~johnnyrichard/olang-devel
olang/patches/.build.yml: SUCCESS in 16s
[docs: fix git send-email config instruction][0] from [Carlos Maniero][1]
[0]: https://lists.sr.ht/~johnnyrichard/olang-devel/patches/49460
[1]: mailto:carlos@maniero.me
✓ #1149191 SUCCESS olang/patches/.build.yml https://builds.sr.ht/~johnnyrichard/job/1149191
^ permalink raw reply [flat|nested] 83+ messages in thread
end of thread, other threads:[~2024-09-27 21:11 UTC | newest]
Thread overview: 83+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2024-05-12 14:30 [PATCH olang 0/4] comment based integration tests Carlos Maniero
2024-05-12 14:30 ` [PATCH olang 1/4] tests: add comment based integration tests mechanism Carlos Maniero
2024-05-12 14:30 ` [PATCH olang 2/4] tests: remove previous integration tests structure Carlos Maniero
2024-05-12 14:30 ` [PATCH olang 3/4] tests: include integration tests for function parser errors Carlos Maniero
2024-05-12 14:30 ` [PATCH olang 4/4] tests: print integration tests TODOs Carlos Maniero
2024-05-12 14:31 ` [olang/patches/.build.yml] build success builds.sr.ht
2024-08-09 19:42 ` [PATCH olang 0/4] comment based integration tests Johnny Richard
2024-08-21 15:58 ` Johnny Richard
-- strict thread matches above, loose matches on Subject: below --
2024-09-27 23:07 [PATCH olang v2 1/2] ast: add function call node Johnny Richard
2024-09-27 21:11 ` [olang/patches/.build.yml] build success builds.sr.ht
2024-09-25 23:20 [PATCH olang v1 2/2] parser: add support for parsing function calls Johnny Richard
2024-09-25 21:22 ` [olang/patches/.build.yml] build success builds.sr.ht
2024-09-25 18:39 [PATCH olang] tests: fix diff error output Carlos Maniero
2024-09-25 18:39 ` [olang/patches/.build.yml] build success builds.sr.ht
2024-09-25 18:30 [PATCH olang] parser: parse multiple function into a single translation unit Carlos Maniero
2024-09-25 18:31 ` [olang/patches/.build.yml] build success builds.sr.ht
2024-09-23 22:19 [PATCH olang v1 2/3] lexer: add token comma Johnny Richard
2024-09-23 22:23 ` [olang/patches/.build.yml] build success builds.sr.ht
2024-09-23 11:43 [PATCH olang 2/2] ast: permit multi declarations on translation unit Carlos Maniero
2024-09-23 11:44 ` [olang/patches/.build.yml] build success builds.sr.ht
2024-09-23 10:11 [PATCH olang v1 3/3] naming: rename all identifier symbols to id Carlos Maniero
2024-09-23 10:12 ` [olang/patches/.build.yml] build success builds.sr.ht
2024-09-22 0:46 [PATCH olang v2 4/4] codegen: operate mov instructions based on the symbol's type Carlos Maniero
2024-09-22 0:47 ` [olang/patches/.build.yml] build success builds.sr.ht
2024-09-21 21:02 [PATCH olang v1 2/2] tests: build: add parallelization support for unit tests Johnny Richard
2024-09-21 21:05 ` [olang/patches/.build.yml] build success builds.sr.ht
2024-09-21 8:25 [PATCH olang 5/5] codegen: perform mov instructions based on variable type Carlos Maniero
2024-09-21 8:26 ` [olang/patches/.build.yml] build success builds.sr.ht
2024-09-21 1:13 [PATCH olang 5/5] codegen: preserve function's variable stack location Carlos Maniero
2024-09-21 1:13 ` [olang/patches/.build.yml] build success builds.sr.ht
2024-09-21 0:20 [PATCH olang v1 3/3] codegen: add support scopes and symbols lookups for var Johnny Richard
2024-09-21 0:23 ` [olang/patches/.build.yml] build success builds.sr.ht
2024-09-17 15:14 [PATCH olang] cli: add libc error handling Carlos Maniero
2024-09-17 15:15 ` [olang/patches/.build.yml] build success builds.sr.ht
2024-09-17 13:43 [PATCH olang v1] remove unused examples programs Johnny Richard
2024-09-17 11:43 ` [olang/patches/.build.yml] build success builds.sr.ht
2024-09-17 12:46 [PATCH olang v1 4/4] docs: info: add instructions to install/uninstall olang Johnny Richard
2024-09-17 10:48 ` [olang/patches/.build.yml] build success builds.sr.ht
2024-09-16 16:29 [PATCH olang v1 3/3] docs: remove pandoc dependency for man docs Johnny Richard
2024-09-16 14:31 ` [olang/patches/.build.yml] build success builds.sr.ht
2024-09-11 1:03 [PATCH olang v1 2/2] parser: add var definition and reference support Johnny Richard
2024-09-10 23:05 ` [olang/patches/.build.yml] build success builds.sr.ht
2024-08-25 13:16 [PATCH olang v2 2/2] codegen: x86_64: implement binary operations Johnny Richard
2024-08-25 13:26 ` [olang/patches/.build.yml] build success builds.sr.ht
2024-08-21 3:39 [PATCH olang 1/2] tests: add comment based integration tests mechanism Carlos Maniero
2024-08-21 3:41 ` [olang/patches/.build.yml] build success builds.sr.ht
2024-08-13 18:55 [PATCH olang v2 2/2] ast: inline ast_node_data_t union typedef Johnny Richard
2024-08-13 18:04 ` [olang/patches/.build.yml] build success builds.sr.ht
2024-04-27 12:14 [PATCH olang v1 2/2] codegen: x86_64: implement binary operations Johnny Richard
2024-04-27 11:21 ` [olang/patches/.build.yml] build success builds.sr.ht
2024-04-18 23:08 [PATCH olang v1] parser: fix parse expression with binop chain Johnny Richard
2024-04-18 22:11 ` [olang/patches/.build.yml] build success builds.sr.ht
2024-04-18 22:18 [PATCH olang v1] parser: add missing <= and >= binary operators Johnny Richard
2024-04-18 21:22 ` [olang/patches/.build.yml] build success builds.sr.ht
2024-04-18 21:58 [PATCH olang v1] docs: spec: add %, <= and >= binary operators Johnny Richard
2024-04-18 21:02 ` [olang/patches/.build.yml] build success builds.sr.ht
2024-04-16 23:51 [PATCH olang v1] Revert "docs: spec: postpone assignment operators" Johnny Richard
2024-04-16 22:56 ` [olang/patches/.build.yml] build success builds.sr.ht
2024-04-16 23:35 [PATCH olang v2] docs: spec: add binary expressions Johnny Richard
2024-04-16 22:40 ` [olang/patches/.build.yml] build success builds.sr.ht
2024-04-15 18:20 [PATCH olang v1] spec: ebnf: add binary expressions Johnny Richard
2024-04-15 17:43 ` [olang/patches/.build.yml] build success builds.sr.ht
2024-04-08 4:38 [PATCH olang v2 2/2] docs: spec: add variables and constants specification Carlos Maniero
2024-04-08 4:39 ` [olang/patches/.build.yml] build success builds.sr.ht
2024-03-29 1:59 [PATCH olang] linter: turn off clang-format to keep retro compatibility with v16 Johnny Richard
2024-03-29 0:59 ` [olang/patches/.build.yml] build success builds.sr.ht
2024-03-29 0:33 [PATCH olang] site: change look and feel and rewrite home introduction section Johnny Richard
2024-03-28 23:33 ` [olang/patches/.build.yml] build success builds.sr.ht
2024-03-24 16:12 [PATCH olang v3] docs: create o programming language spec Johnny Richard
2024-03-24 15:16 ` [olang/patches/.build.yml] build success builds.sr.ht
2024-03-19 20:18 [PATCH olang v2] docs: create o programming language spec Johnny Richard
2024-03-19 19:20 ` [olang/patches/.build.yml] build success builds.sr.ht
2024-03-19 19:57 [PATCH olang v1 3/3] codegen: add compiler support to linux aarch64 arch Johnny Richard
2024-03-19 19:00 ` [olang/patches/.build.yml] build success builds.sr.ht
2024-03-18 8:39 [PATCH olang v3 3/3] parser: add all binary operation expressions Johnny Richard
2024-03-18 7:43 ` [olang/patches/.build.yml] build success builds.sr.ht
2024-03-17 21:29 [PATCH olang v2 3/3] parser: add all binary operation expressions Johnny Richard
2024-03-17 20:37 ` [olang/patches/.build.yml] build success builds.sr.ht
2024-03-13 21:21 [PATCH olang v1 3/3] parser: add basic arithmetic expressions '+' '*' '/' '-' Johnny Richard
2024-03-13 20:29 ` [olang/patches/.build.yml] build success builds.sr.ht
2024-03-13 12:44 [PATCH olang v3] refactor: rename zero programming language to olang Fabio Maciel
2024-03-13 12:45 ` [olang/patches/.build.yml] build success builds.sr.ht
2024-03-12 19:35 [PATCH olang v1] refactor: rename zero programming language to olang Johnny Richard
2024-03-12 18:40 ` [olang/patches/.build.yml] build success builds.sr.ht
2024-03-11 8:48 [PATCH olang] site: change dns to o-lang.org Johnny Richard
2024-03-11 7:50 ` [olang/patches/.build.yml] build success builds.sr.ht
2024-03-09 0:05 [RFC PATCH olang v1] docs: create zero programming language specification Johnny Richard
2024-03-08 23:09 ` [olang/patches/.build.yml] build success builds.sr.ht
2024-03-14 4:29 ` Ricardo Kagawa
2024-03-14 22:43 ` Johnny Richard
2024-03-08 23:13 [PATCH olang v1] ast: add ast_node root for the entire program Johnny Richard
2024-03-08 22:13 ` [olang/patches/.build.yml] build success builds.sr.ht
2024-03-08 22:39 [PATCH olang v2 3/3] tests: add tests for the minimal possible olang program Carlos Maniero
2024-03-08 22:40 ` [olang/patches/.build.yml] build success builds.sr.ht
2024-03-07 23:23 [PATCH olang 3/3] tests: add tests for the minimal possible olang program Carlos Maniero
2024-03-07 23:24 ` [olang/patches/.build.yml] build success builds.sr.ht
2024-03-01 22:24 [PATCH olang v2 4/4] parser: create simplified parser for tiny AST Johnny Richard
2024-03-01 21:32 ` [olang/patches/.build.yml] build success builds.sr.ht
2024-02-28 19:04 [PATCH olang v1 4/4] parser: create simplified parser for tiny AST Johnny Richard
2024-02-28 18:11 ` [olang/patches/.build.yml] build success builds.sr.ht
2024-02-28 14:25 [PATCH olang v3] arena: optimization: ensure alignment memory access Carlos Maniero
2024-02-28 14:26 ` [olang/patches/.build.yml] build success builds.sr.ht
2024-02-28 12:37 [PATCH olang v2] cli: replace memory allocation malloc -> arena Johnny Richard
2024-02-28 11:39 ` [olang/patches/.build.yml] build success builds.sr.ht
2024-02-27 19:59 [PATCH olang v2 2/2] utils: create hash map data structure Johnny Richard
2024-02-27 19:01 ` [olang/patches/.build.yml] build success builds.sr.ht
2024-02-24 20:40 [PATCH olang] test: fix suite name for list_test and arena_test Johnny Richard
2024-02-24 19:42 ` [olang/patches/.build.yml] build success builds.sr.ht
2024-02-22 19:09 [PATCH olang] cli: replace memory allocation malloc -> arena Johnny Richard
2024-02-22 18:11 ` [olang/patches/.build.yml] build success builds.sr.ht
2024-02-22 18:38 [PATCH olang] docs: add DCO information on hacking page Johnny Richard
2024-02-22 17:41 ` [olang/patches/.build.yml] build success builds.sr.ht
2024-02-22 18:24 [PATCH olang] build: rename 0c.c file to main.c Johnny Richard
2024-02-22 17:26 ` [olang/patches/.build.yml] build success builds.sr.ht
2024-02-21 22:20 [PATCH olang 2/2] utils: create hash map data structure Johnny Richard
2024-02-21 21:24 ` [olang/patches/.build.yml] build success builds.sr.ht
2024-02-21 15:09 [PATCH olang v2] arena: optimization: make arena 8 bits aligned Carlos Maniero
2024-02-21 15:09 ` [olang/patches/.build.yml] build success builds.sr.ht
2024-02-21 5:52 [PATCH olang] arena: optimization: make arena 8 bits aligned Carlos Maniero
2024-02-21 5:53 ` [olang/patches/.build.yml] build success builds.sr.ht
2024-02-20 23:37 [PATCH olang] utils: add linked-list Carlos Maniero
2024-02-20 23:37 ` [olang/patches/.build.yml] build success builds.sr.ht
2024-02-20 17:35 [PATCH olang v3] utils: add arena Carlos Maniero
2024-02-20 17:41 ` [olang/patches/.build.yml] build success builds.sr.ht
2024-02-19 20:42 [PATCH olang v5 4/4] lexer: test: add integration tests for --dump-tokens Carlos Maniero
2024-02-19 20:48 ` [olang/patches/.build.yml] build success builds.sr.ht
2024-02-19 1:44 [PATCH olang v3 2/2] lexer: create --dump-tokens cli command Johnny Richard
2024-02-19 0:47 ` [olang/patches/.build.yml] build success builds.sr.ht
2024-02-18 0:50 [PATCH olang 2/2] tests: add unit tests configuration Carlos Maniero
2024-02-18 0:55 ` [olang/patches/.build.yml] build success builds.sr.ht
2024-02-17 21:04 [PATCH olang] docs: deploy: replace shrt.site domain by olang.johnnyrichard.com Johnny Richard
2024-02-17 20:03 ` [olang/patches/.build.yml] build success builds.sr.ht
2024-02-17 20:38 [PATCH olang] docs: build: fix docs publishing task Johnny Richard
2024-02-17 19:37 ` [olang/patches/.build.yml] build success builds.sr.ht
2024-02-17 20:12 [PATCH olang] docs: add mobile version Carlos Maniero
2024-02-17 20:17 ` [olang/patches/.build.yml] build success builds.sr.ht
2024-02-17 18:40 [PATCH olang v2] docs: add HACKING documentation Carlos Maniero
2024-02-17 18:45 ` [olang/patches/.build.yml] build success builds.sr.ht
2024-02-17 18:29 [PATCH olang v2] docs: add white mode support Carlos Maniero
2024-02-17 18:34 ` [olang/patches/.build.yml] build success builds.sr.ht
2024-02-17 17:46 [PATCH olang] docs: add white-mode support Carlos Maniero
2024-02-17 17:51 ` [olang/patches/.build.yml] build success builds.sr.ht
2024-02-17 16:22 [PATCH olang] docs: add pandoc Carlos Maniero
2024-02-17 16:27 ` [olang/patches/.build.yml] build success builds.sr.ht
2024-02-16 16:24 [PATCH olang v2] docs: add sphinx documentation support Johnny Richard
2024-02-16 15:26 ` [olang/patches/.build.yml] build success builds.sr.ht
2024-02-16 16:23 [PATCH olang] docs: build: add deployment script Carlos Maniero
2024-02-16 16:28 ` [olang/patches/.build.yml] build success builds.sr.ht
2024-02-16 8:59 [PATCH olang] docs: add sphinx documentation support Johnny Richard
2024-02-16 8:01 ` [olang/patches/.build.yml] build success builds.sr.ht
2024-02-16 3:07 [PATCH olang v3 2/2] tests: add integration test setup Carlos Maniero
2024-02-16 3:12 ` [olang/patches/.build.yml] build success builds.sr.ht
2024-02-15 16:21 [PATCH olang 2/2] tests: add integration test setup Carlos Maniero
2024-02-15 16:27 ` [olang/patches/.build.yml] build success builds.sr.ht
2024-02-13 20:55 [PATCH olang] docs: fix git send-email config instruction Carlos Maniero
2024-02-13 21:00 ` [olang/patches/.build.yml] build success builds.sr.ht
Code repositories for project(s) associated with this public inbox
https://git.johnnyrichard.com/olang.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox