Giter Site home page Giter Site logo

rustic's People

Contributors

abigailbuccaneer avatar eddyb avatar miselin avatar orthographic-pedant avatar wolfwood avatar

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

rustic's Issues

Document license and contributors better.

Currently the license header contains my name and there is no central CONTRIB file or similar that offers a central way to figure out who has contributed code to Rustic.

In the interest of giving credit where credit is due, this should be improved.

Use rustpkg to compile the kernel crate

Currently dependencies don't work too well in the Makefile. Ideally we'd use something like rustpkg to manage the actual compilation of the kernel crate (and any other important crates), and then link the results together with the C and ASM glue.

Because we have no real way of determining a recompile is necessary when anything other than main.rs changes, we will probably just have to run rustpkg every time make is executed. This is a real incentive to make sure we're avoiding as much cruft in the code as possible to optimise compile time.

This would need to be done in such a way that cross-compiling doesn't break. Fortunately I do a reasonable amount of development on OSX where we cross from the Mach host to ELF target, so it will be immediately obvious if things are broken.

Define and document the code style and module structure.

Inconsistency should be avoided where possible.

Rust itself uses UpperCamelCase for non-primitive type names and traits, while the current code base has a few structures using lowercasewithnospaces.

For the module structure, for example, io/x86 is preffered over arch/x86/io, and allows for easy automatic import:

// in io/mod.rs:
#[cfg(arch="x86")]
pub use x86::*;
// everything exported by io/x86.rs or io/x86/mod.rs shows up in io.

C code in rustic

Hi,
I wonder if you should use C code in rustic. I mean it would be better if you use only asm (inline or external) and Rust, like rustboot does.
It's just a sugestion from a poor newbie. Good work! Go on!

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    ๐Ÿ–– Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. ๐Ÿ“Š๐Ÿ“ˆ๐ŸŽ‰

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google โค๏ธ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.