spotandjake / brisklinker

A General Purpose Wasm Linker Built For The Brisk Programming Language

About Me

Hi my name is Jake, I have been programming for approximatly 7 years, with an interest particuarly in web. Over the past 3 years I have moved to being interested in programming language design and compilers built on webassembly.

Brisk

My favourite project is my uncompleted programming language Brisk, I am building it with the goal of educating myself on compiler design and low level webassembly, counter intuituvly its written primarly in Typescript with the linker portion being written in grain this is because Typescript is very similar to brisk syntactically and should make bootstrapping easier one day.

Interests

• 🔭 I’m currently working on Brisk and grain!
• 📫 How to reach me: Discord: Spotandjake#1510
• ⚡ Fun fact: I love Typescript

Languages

Languages I Like To Use

Languages I Know

Languages I Have Written

Languages I want To Learn

Stats

brisklinker's Issues

Rebuild The Linking Info Section

Rebuild The Linking Info Section to allow caching smaller builds and linking those together.

Improve WriteFile

Until Grain has a user friendly file system module, we need to implement our own user friendly functions we want to make our writeFile function not fail if the file already exists.

Sort The Dependency Graph

We want to properly sort the dependency graph, so we ensure that module initialization happens correctly in the right order, This is currently not very easy we can look at the v1 branch of the compiler to check how we did this before. Once #4 is completed This will be far easier.

Use Grain File System Libary

Once grain gets a user friendly file system libary we want to use that over our own wrappers arround the basic file libary that is provided.

Once this is closed we can close #2 if it isnt completed yet.

Use Grain Path Libary

Grain v0.5.5 added the path module currently we use a hacky solution that only works because the brisk compiler handles the paths in a specific way. We want to change this over to the path module to make the input more robust.

Consider Merging Duplicate Types

Consider Merging Duplicate Types When Rebuilding the type section it wouldnt be very hard, and would lower binary size.

Use Grain Command Line Argument Libary

Once Grain Gets A Libary For Making CLI Tools we should use it for more robust command line arugment parsing.

Support Decoding Imports

Support Decoding Table And Memory Imports

Use Grain Graph Module for our dependency graph

Once grain adds a graph module we want to use this over the way we sort dependencys, as our method works but just barely and isnt very helpful for anything else, our method also is really complicated compared to using a graph.

Consider Making A Decoder And Encoder Libary

Currently we encode and decode inline which isnt terrible but is a little messy if we did it we broke this functionality into modules it would be better and it would contribute to the grain ecosystem.

Support Encoding Imports

Support Encoding Table And Memory Imports.