I tried to transpile the code in the document but doesn't seem to work. After transpiled the code, dist directory was created but the code wasn't converted to the .cpp file.

Things added/changed:

• Merge the GitHub Actions workflows. This will:
  • Make things cleaner.
  • Run for all OSes on the same workflow.
  • Seamlessly check all jobs in one place (example).
  • Run directly on all pull requests and multiple branches.

Detailed description

With a .github repository, you can:

• Have a predefined issue, PR, and funding templates for all repositories. To avoid duplication, you can also have a Code of Conduct, contributing, and security policy. Licenses will not take effect on the other repositories.
  • This can be overridden if a particular repository has other templates.
• Make a customized profile for the organization just like with GitHub users (example.
• Include any links and information about Jule, as well as add images and add a .github-private for only the team members.

Context

IMO, this would make the GitHub organization much more elegant as well as give users the option to quickly check what the project is about.

Possible implementation

Add .github and .github-private repositories for organization customization.

Additional information

If you need any help with this, feel free to contact me via Discord: Panquesito7#3723

Proposal

We should use the newly provided GitHub issue forms. These can prevent blank issues or issues without enough information. We can mark fields as optional or required, making things much more efficient, IMO.

Check the official GitHub blog about this: https://github.blog/changelog/2021-06-23-issues-forms-beta-for-public-repositories/

Additional

I want to work on this. 🙂

https://github.com/jule-lang/jule/blob/main/localization/turkish.json#L121 https://github.com/jule-lang/jule/blob/main/localization/english.json#L22 https://github.com/jule-lang/jule/blob/main/localization/english.json#L23 https://github.com/jule-lang/jule/blob/main/localization/english.json#L24 https://github.com/jule-lang/jule/blob/main/localization/english.json#L25 https://github.com/jule-lang/jule/blob/main/localization/english.json#L87 https://github.com/jule-lang/jule/blob/main/localization/english.json#L50 https://github.com/jule-lang/jule/blob/main/localization/english.json#L59 https://github.com/jule-lang/jule/blob/main/localization/english.json#L67 https://github.com/jule-lang/jule/blob/main/localization/english.json#L68

it may be better to put the word underline instead of compound

current code

"notimpl_trait_def": ...

desired

"not_impl_trait_def": ...

Hİ Mertcan! Well done, Jule is very nice programming language :) It's just wrong like this:

main() {
    const a int32 = 5;
    var b int32 = 25;
    outln(div(b, a));
}

div(x float64, y float64) float64 {
  ret x / y;
}

As a result, g++ reports incorrect code:

x.cxx: In function 'void _main()': x.cxx:205:15: error: '_b_a' was not declared in this scope; did you mean '_b'? 205 | _outln(_div(_b_a)); | ^~~~ | _b

What would you like to share?

The some codes in the standard library are adapted from Go, but do not follow the license of Go and do not meet the requirements.

Additional information

No response

Detailed description

For security reasons, when a vulnerability is found in the code, it should be reported to the maintainers/administrators rather than making an issue on GitHub; otherwise, everything could be exposed. It might be dangerous as well.

More information at https://docs.github.com/es/code-security/getting-started/adding-a-security-policy-to-your-repository

Context

In case a vulnerability in the code is found, the users can check the security policy to know how to report vulnerabilities properly. This will also make it much easier for the maintainers as well for the users and the community using the code.

Possible implementation

No response

Additional information

If you need any help implementing this, let me know. 🙂

when i transpile this jule code, i get the decimal value of the chars in the "test" string:

fn main() {
    let s = "test"
    for _, b in s {
        outln(b)
    }
}

// OUTPUT
116
101
115
116

is this expected behavior, because it doesn't l like that in the docs?

Detailed description

Add a pull request template to the repository to let maintainers know of the change easier and more.

Context

A pull request template will make it easier for the maintainers and PR creators as well to make sure they've done everything correctly and have added the required information.

Possible implementation

Add a PR template to the repository.

Additional information

No response