БЕГЕМОТИКОВ МОЖНО! Войти !bnw Сегодня Клубы
Привет, TbI — HRWKA! 1017.2 пользователей не могут ошибаться! Официальная конфочка бнвача: bnw@conference.jabber.ru
говно5743
?5720
прекрасное4925
говнорашка4233
хуита3598
anime2574
linux2396
music2207
bnw2187
log1974
рашка1847
pic1835
ололо1730
быдло1418
украина1313
гімно1062
дыбр1038
роботы_не_одобряют846
сталирасты802
bnw_ppl787

https://www.mercurial-scm.org/wiki/OxidationPlan "Using Rust in Mercurial This page describes the plan and status for leveraging the Rust programming language in Mercurial. Why use Rust? Today, Mercurial is a Python application. It uses Python C extensions in various places to achieve better performance. There are many advantages to being a Python application. But, there are significant disadvantages. Performance is a significant pain point with Python. There are multiple facets to the performance problem: Startup overhead General performance overhead compared to *native* code GIL interfering with parallel execution It takes several dozen milliseconds to start a Python interpreter and load the Mercurial Python modules. If you have many extensions loaded, it could take well over 100ms just to effectively get to a Mercurial command's main function. Reports of over 250ms are known. While the command itself may complete in mere milliseconds, Python overhead has already made hg seem non-instantaneous to end-users. A few years ago, we measured that CPython interpreter startup overhead amounted to 10-18% of the run time of Mercurial's test harness. 100ms may not sound like a lot. But it is enough to give the perception that Mercurial is slower than tools like Git (which can run commands in under 10ms). There are also situations like querying hg for shell prompts that require near-instantaneous execution. Mercurial is also heavily scripted by tools like IDEs. We want these tools to provide results near instantaneously. If people are waiting over 100ms for results from hg, it makes these other tools feel sluggish. There are workarounds for startup overhead problems: the CommandServer (start a persistent process and issue multiple commands to it) and CHg (a C binary that speaks with a Mercurial command server and enables chg commands to execute without Python startup overhead). chg's very existence is because we need hg to be a native binary in order to avoid Python startup overhead. If hg weren't a Python script, we wouldn't need chg to be a separate program. Python is also substantially slower than native code. PyPy can deliver substantially better performance than CPython. And some workloads with PyPy might even be faster than native code due to JIT. But overall, Python is slower than native code. But even with PyPy's magical performance, we still have the GIL. Python doesn't allow you to execute CPU-bound Python code on multiple threads. If you are CPU bound, you need to offload that work to an extension (which releases the GIL when it executes hot code) or you spawn multiple processes. Since Mercurial needs to run on Windows (where new process overhead is ~10x worse than POSIX and is a platform optimized for spawning threads - not processes), many of the potential speedups we can realize via concurrency are offset on Windows by new process overhead and Python startup overhead. We need thread-level concurrency on Windows to help with shorter-lived CPU-bound workloads. This includes things like revlog reading (which happens on nearly every Mercurial operation). In addition to performance concerns, Python is also hindering us because it is a dynamic programming language. Mercurial is a large project by Python standards. Large projects are harder to maintain. Using a statically typed programming language that finds bugs at compile time will enable us to make wide-sweeping changes more fearlessly. This will improve Mercurial's development velocity. Today, when performance is an issue, Mercurial developers currently turn to C. But we treat C as a measure of last resort because it is just too brittle. It is too easy to introduce security vulnerabilities, memory leaks, etc. On top of vanilla C, the Python C API is somewhat complicated. It takes significantly longer to develop C components because the barrier to writing bug-free C is much higher..."
#ZFY03P (0+1) / @o01eg / 7 дней назад
https://blog.rust-lang.org/2017/11/22/Rust-1.22.html "What’s in 1.22.0 and 1.22.1 stable The headline feature for this release is one many have been anticipating for a long time: you can now use ? with Option<T>! About a year ago, in Rust 1.13, we introduced the ? operator for working with Result<T, E>. Ever since then, there’s been discussion about how far ? should go: should it stay only for results? Should it be user-extensible? Should it be usable with Option<T>? In Rust 1.22, basic usage of ? with Option<T> is now stable. This code will now compile: fn try_option_some() -> Option<u8> { let val = Some(1)?; Some(val) } assert_eq!(try_option_some(), Some(1)); fn try_option_none() -> Option<u8> { let val = None?; Some(val) } assert_eq!(try_option_none(), None); However, this functionality is still a bit limited; you cannot yet write code that mixes results and options with ? in the same function, for example. This will be possible in the future, and already is in nightly Rust; expect to hear more about this in a future release. Types that implement Drop are now allowed in const and static items. Like this: struct Foo { a: u32 } impl Drop for Foo { fn drop(&mut self) {} } const F : Foo = Foo { a : 0 }; static S : Foo = Foo { a : 0 }; This change doesn’t bring much on its own, but as we improve our ability to compute things at compile-time, more and more will be possible in const and static. Additionally, some small quality-of-life improvements: Two recent compiler changes should speed up compiles in debug mode. We don’t have any specific numbers to commit to with these changes, but as always, compile times are very important to us, and we’re continuing to work on improving them. T op= &T now works for primitive types, which is a fancy way of saying: let mut x = 2; let y = &8; // this didn&#39;t work, but now does x += y; Previously, you’d have needed to write x += *y in order to de-reference, so this solves a small papercut."
#6P73I3 (1+1) / @o01eg / 18 дней назад
Не прошло и ста лет https://github.com/nc4rrillo/indigo
#4060VN (0+1) / @o01eg / 34 дня назад
http://jnep.sumdu.edu.ua:8080/download/numbers/2017/5/articles/Proof_JNEP_05015.pdf Моделирование магнитных гетероструктур с использованием языка Rust и MPI. Rust в компьютерное моделирование физических систем! Долой гегемонию C++!
#QR5UGE (4+1) / @corpse / 44 дня назад
https://twitter.com/sdroege_/status/916357166088511488 "Naively re-implemented some @gstreamer C code in @rustlang for fun & result was ~1.7x faster. Zero-cost abstractions? I&#39;d say negative-cost Now optimizing the C code. There&#39;s no reason why it should be slower. But Rust apparently made it easier in this case to write fast code"
#E56948 (1+1) / @o01eg / 66 дней назад
> lexszero‎: http://securityaffairs.co/wordpress/51126/malware/linux-trojan-irc16.html ура хороший системный яп
#YI9M3Z (2+3) / @ndtimofeev / 91 день назад
https://blog.rust-lang.org/2017/08/31/Rust-1.20.html "Rust 1.20 adds the ability to define “associated constants” as well: struct Struct; impl Struct { const ID: u32 = 0; } fn main() { println!("the ID of Struct is: {}", Struct::ID); } That is, the constant ID is associated with Struct. Like functions, associated constants work with traits and enums as well. Traits have an extra ability with associated constants that gives them some extra power. With a trait, you can use an associated constant in the same way you’d use an associated type: by declaring it, but not giving it a value. The implementor of the trait then declares its value upon implementation"
#VXV2GO (0) / @o01eg / 102 дня назад
Красота, через три месяца в релизе: https://play.rust-lang.org/?gist=80cf2488c9daaedf43c73181a9bf2edb&version=nightly
#QXR9RF (0+1) / @o01eg / 103 дня назад
НИ ЕДИНОГО СЕГФОЛТА!!!! https://habrahabr.ru/company/erlyvideo/blog/334912/ "А чего там про Rust Вот как раз стример у нас ржавый. Целая пачка unsafe кода, автогенеренного из сишного кода SDK с помощью bindgen, подпатченый биндинг к libc (постараемся залить патч в апстрим) и дальше реализация RTSP на tokio. Даже уже есть возможность посмотреть видео с камеры в обычном браузере — это недостижимая роскошь для китайских камер, которые поголовно требуют установку ActiveX. Структура очень непривычна после эрланга: ведь тут нет процессов и сообщений, есть каналы, а с ними всё становится немножко по-другому. Как я уже выше писал, современно написанный код с правильной организацией дает возможность раздавать видео не 2-3 клиентам, а более 50 без какой-либо просадки производительности. Важный момент: за время разработки пока не случилось ни единого сегфолта. Пока есть стойкое ощущение, что Rust заставляет писать так, как в принципе пишут хорошие поседевшие сишники, повидавшие всякого нехорошего. Так что пока всё нравится. В течение августа есть планы закончить работу по базовому сценарию, так что есть вопрос к аудитории, который идет в опросе. Ну и задавайте вопросы, которые возникли."
#NGXQPU (0+1) / @o01eg / 129 дней назад
https://spb.hh.ru/vacancy/21894554 "Требования Опыт backend-разработки на Rust не менее 2 лет."
#ZH5DRP (0) / @o01eg / 153 дня назад
У меня одного метод https://docs.rs/tokio-postgres/0.2.3/tokio_postgres/struct.Connection.html#method.execute зависает в реакторе? query в асинхронной версии и execute в синхронной спокойно работают, а этот висит со статусом idle и не завершает свой Future.
#8PD492 (0+1) / @o01eg / 166 дней назад
Хозяйке на заметку: let future_returns_db_connection = ...; let prog = future_returns_db_connection.and_then(|db_connection| { your_stream_wants_to_work_with_db.fold(db_connection, |also_db_connection, value| { also_db_connection.just_another_db_query_moveouts_connection_and_return_a_new_one() }) })
#MBJO51 (1) / @o01eg / 174 дня назад
Хозяйке на заметку: fn main() { let mut core = Core::new().expect("Can&#39;t create Tokio Core"); let handle = core.handle(); // Use only one Ctrl+C signal. let ctrl_c = tokio_signal::ctrl_c(&handle).flatten_stream().take(1).map(|_| false); let interval = Interval::new(Duration::from_secs(1), &handle).expect("Cann&#39;t create timer").map(|_| true); // Process each ctrl-c as it comes in let prog = ctrl_c .select(interval) .take_while(|c| Ok(*c)) // stop when Ctrl+C .for_each(|c| { println!("{:?}", c); future::ok(()) }); match core.run(prog) { Ok(o) => println!("Finish: {:?}", o), Err(e) => println!("Error: {}", e), }; }
#LC4YX3 (2) / @o01eg / 176 дней назад
https://blog.rust-lang.org/2017/06/08/Rust-1.18.html "What’s in 1.18.0 stable As usual, Rust 1.18.0 is a collection of improvements, cleanups, and new features. One of the largest changes is a long time coming: core team members Carol Nichols and Steve Klabnik have been writing a new edition of “The Rust Programming Language”, the official book about Rust. It’s being written openly on GitHub, and has over a hundred contributors in total. This release includes the first draft of the second edition in our online documentation. 19 out of 20 chapters have a draft; the draft of chapter 20 will land in Rust 1.19. When the book is done, a print version will be made available through No Starch Press, if you’d like a paper copy. We’re still working with the editors at No Starch to improve the text, but we wanted to start getting a wider audience now. The new edition is a complete re-write from the ground up, using the last two years of knowledge we’ve gained from teaching people Rust. You’ll find brand-new explanations for a lot of Rust’s core concepts, new projects to build, and all kinds of other good stuff. Please check it out and let us know what you think! As for the language itself, an old feature has learned some new tricks: the pub keyword has been expanded a bit. Experienced Rustaceans will know that items are private by default in Rust, and you can use the pub keyword to make them public. In Rust 1.18.0, pub has gained a new form: pub(crate) bar; The bit inside of () is a ‘restriction’, which refines the notion of how this is made public. Using the crate keyword like the example above means that bar would be public to the entire crate, but not outside of it. This makes it easier to declare APIs that are “public to your crate”, but not exposed to your users. This was possible with the existing module system, but often very awkward. You can also specify a path, like this: pub(in a::b::c) foo; This means “usable within the hierarchy of a::b::c, but not elsewhere.” This feature was defined in RFC 1422 and is documented in the reference. For our Windows users, Rust 1.18.0 has a new attribute, #![windows_subsystem]. It works like this: #![windows_subsystem(console)] #![windows_subsystem(windows)] These control the /SUBSYSTEM flag in the linker. For now, only console and windows are supported. When is this useful? In the simplest terms, if you’re developing a graphical application, and do not specify windows, a console window would flash up upon your application’s start. With this flag, it won’t. Finally, Rust’s tuples, enum variant fields, and structs (without #[repr]) have always had an undefined layout. We’ve turned on automatic re-ordering, which can result in smaller sizes through reducing padding..."
#2DINCJ (0+1) / @o01eg / 186 дней назад

http://blog.japaric.io/quickstart/
↖ статья о том как модно писать на русте под stm32 на этой неделе.
tldr: берем пару крейтов для базового cortex-m, генерируем 200 килострок кода для работы с периферией из SVD (til есть репозиторий с машиночитаемыми описаниями регистров кучи мк), ..., выгода. даже дебагать гдбшечкой можно, для нормальной жизни не хватает только scheduler/rtos или чего-то подобного.
а вот zinc.rs на который я фапал некоторое время назад, кажется, помер.

#2OA42D (6) / @lexszero / 226 дней назад
#3ABU4N (0+1) / @o01eg / 231 день назад
ipv6 ready BnW для ведрофона BnW на Реформале Викивач Котятки

Цоперайт © 2010-2016 @stiletto.