Rust

Rust is a systems programming language created by Mozilla. It is similar to C++, but is designed for improved memory safety without sacrificing performance.
Here are 26,745 public repositories matching this topic...
Describe the bug you encountered:
If you use bat on C# source files (.cs, .xaml and others), a space appears in the first line. This is due to byte order mark (BOM)
Maybe reproduced for others files on Windows systems
https://en.wikipedia.org/wiki/Byte_order_mark#Byte_order_marks_by_encoding
Sample file with BOM:
[Program.cs.txt](https://github.com/sharkdp/bat/files/7420061/Program
I'd like to see a recipe for creating a simple tauri project with shadow-cljs so I can get up and running quickly.
Here's what I think it should look like: https://github.com/wildwestrom/tauri-shadow-cljs
So far it needs a few things, like a convenience script for development and building.
I also don't know if this is the best way to go about integrating shadow-cljs with tauri. For example, h
-
Updated
Nov 18, 2021 - Rust
-
Updated
Nov 18, 2021 - Rust
We should find a way to have only one file related to the docker image CI instead of two, for maintenance reasons.
Here are the current files:
- https://github.com/meilisearch/MeiliSearch/blob/main/.github/workflows/publish-docker-latest.yml: publish the git tag as docker tag
- https://github.com/meilisea
Combining fd and rg
fd 8.2.1 on Windows 10
fd --changed-within "2021-10-09" | rg -i xxx
won't return an result.
fd --changed-within "2021-10-09" --exec rg -i xxx
returns the lines macthing xxx but the output is missing the filename where xxx is found.
Any idea how to get the filename where xxx is found?
rg -i xxx
alone returns machting lines including filename
Yew has recently got support for keyed elements, but the documentation lacks any mention of them. A mention should be added in the website, the doc of yew::virtual_dom::key::Key
should be
-
Updated
Nov 20, 2021 - Rust
-
Updated
Nov 20, 2021 - C++
-
Updated
Nov 19, 2021 - Rust
Describe the bug
On non-ansi terminals, such as 9term, the output is quite garbled, filled with ANSI escape codes. sed-ing out these escape codes almost makes it workable, making command output quite visible, but things such as any text input is completely invisible. Looking around there may be already a way to get it to function, it simply requires being a tty... which is a bit hard to do, w
-
Updated
Nov 17, 2021 - Rust
-
Updated
Nov 19, 2021 - Rust
-
Updated
Oct 31, 2021 - Makefile
-
Updated
Nov 19, 2021 - Rust
-
Updated
Nov 9, 2021 - Rust
-
Updated
Nov 19, 2021 - Rust
Right now any StyleSheet
has a list of functions without a default implementation. Implementing a StyleSheet
is really annoying, because you have to override all of the functions and not just the thing you want to change.
I recently wanted to just change the border_radius of a text_input and I had to write the following code.
impl StyleSheet for Styles {
fn active(&self) ->
Describe the bug
Using a time dimension on a runningTotal measure on Snowflake mixes quoted and unquoted columns in the query. This fails the query, because Snowflake has specific rules about quoted columns. Specifically:
- All unquoted column names are treated as upper case
- Quoted column names are case sensitive.
So "date_from" <> date_from
To Reproduce
Steps to reproduce
-
Updated
Nov 20, 2021 - Rust
Ref #94. It might be better for the output to say something like
added: foo (binary file)
than the current
Binary files /dev/null and b/foo differ
It would be neat if you could change the color of the text that shows when the progress bar covers it without changing the background. My motivation is that I enjoy the black background but the default color can be hard to read on dark progress bar colors.
<img width="1423" alt="Screen Shot 2020-06-06 at 11 50 41 AM" src="https://user-images.githubusercontent.com/16331012/83952212-14b8d780-
-
Updated
Nov 19, 2021 - Rust
-
Updated
Nov 20, 2021 - Rust
Created by Graydon Hoare
Released 2010
- Organization
- rust-lang
- Website
- www.rust-lang.org
- Wikipedia
- Wikipedia
Deno strives to be browser compatible where possible; that means we use quite a few Web APIs.
There is not much docs for supported Web APIs at the moment and before 1.0 is released that situation must change. Some of APIs and not fully aligned to spec, while others are not fully implemented (#3557). All that knowledge should be written down and presented to end users to avoid multiple question