-
Notifications
You must be signed in to change notification settings - Fork 168
Use alloc and core crates where they are applicable #331
Conversation
Cc #247. Making it |
As a side note, another thing that can be done to further this effort would be e.g. to use the |
The plan is to create incremental steps towards no_std instead of making everything at once like in #282 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is looking good, apologies for the delay.
bors r+
Build succeeded: |
use core::borrow::Borrow; | ||
use core::fmt; | ||
use core::ops::Range; | ||
use futures::stream::Stream; | ||
use ipfs_unixfs::file::{visit::IdleFileVisit, FileReadFailed}; | ||
use std::borrow::Borrow; | ||
use std::fmt; | ||
use std::ops::Range; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Just noticed while handling local conflicts that these were probably extra. ipfs
should not attempt to be no_std at this time.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Indeed, the ipfs
crate deals with input and output operations that are tied to the underlying OS
First step towards no_std compatibility for unixfs