#Adhoc Testing

[hayleysayshay]

CR twitter having a normal one and deciding CR is the end all be all of targeted activism

I have seen these posts get like 500 likes asking CR to donate and then Matt’s response where he talks about poor mental health but says that he’s given 15k of their own money to Gaza is like, clear they align with a pro Palestine position. And this response has got 28k likes. It’s a very online bubble talking to each other, and they cannot see that they’re posting the same information to each other and aren’t changing any damn minds.

Very high possibility CR can’t say anything on the Critical Role accounts because of their contracts with Amazon. So what if they never post for these people? Maybe just give up and move on?

When I first got into the fandom I saw all this cool clothing merch so I looked for their code of ethics. Couldn’t find one. Emailed the shop/site about it, never got a response. Gave up and moved on.

My genuine position it’s nice when they do do something good, but I have no expectations otherwise, they’re not an ethical company they’re a business.

And it’s totally normal to be disappointed and want to spend your money and time elsewhere, I’m not here to tell you you’re wrong, but I think some twitter activists people have lost sight of a bigger picture by being in a bubble. I just don’t care to centre a damn media company in my activism and have better things to worry about than fucking Critical role.

Like I donate monthly anyway and adhoc donations. I wouldn’t donate to a fundraiser unless there was something amazing offered during it, as a) I prefer to just give straight to the charity as I think that avoids processing fees b) it probably wouldn’t even be in my timezone? Idk people can just donate anyway, people are already well organised and you don’t need Critical Role to do it for you.

Support who you want, but turning other fans not boycotting critical role, the DnD media company, into a litmus test if you’re a good person or not a bit ridiculous here, and a bit unserious.

[tevintersnakes]

Thinking about how the Followers medical training differs from that of doctors from vaults, and general wastelanders.

In terms of textbook and case study information they have far greater access to accurate information than the general wasteland population. In some cases they probably have better information than people taught within vaults because not only do they have pre-war textbooks to go off of but they also have two hundred years worth of adhoc solutions built up. They have enough physician's to be passing around case studies that hinge on the use of limited and alternative supplies to what pre-war hospitals had to build up some standard practices in tight situations. Then of course there is the fact that their practical training leans far more EM & Rural than what any vault dweller doctor is going to see (in a control vault anyway).

Contrast this to vault where you've probably only got a small handful of medical staff. The variety of both case studies and what someone is exposed to over the course of their career is going to be a lot lower.

Followers, by courtesy of the wastes being the wastes are going to get both a higher volume of patients and a much broader variety of cases to work on. Their training as a result is going to be far more well rounded than a vault dweller doctor. Both Followers and vault dwellers at least have far more consistent medical training than the general population of the wastes at least. The general wastes- a lot of people being self taught from whatever textbooks they happen to stumble across. (Can you imagine the wack ways people pronounce the names of some things lmao).

Anyway- OC tie in time here on out.

Antyllus probably has a bit of a culture shock when he starts working alongside them. While he's been out on the road for a while before he joins up with him, he's still in his 20s. That's modern day residency & student age. Sure he's read more case studies and knows more treatment plans than likely anyone around him but he's super textbook focused, growing up in the Institute has provided him with an immense amount of pre-war information but the moment he was out in the wastes??? Having to deal with a lack of supplies and equipment??? His knowledge falls apart.

Proves to the Followers at the Fort that yes he does have medical training and can lay out a treatment plan in response to any case study given to him. Then when let actually practice keeps getting stumped by not having access to equipment he needs, or being unable to carry out the tests required to confirm his suspected diagnoses. 'Cool, great plan Antyllus, but where do you think we'll be getting a CT scanner at this point in time? Where do you think we'll be getting 10mL of y to treat x? Maybe let us take the lead on this one.'

Much to his initial chagrin, he goes from being the most medically competent person around while he was traveling, to being placed into a position equivalent to an intern/junior resident on a probationary period until he gets up to speed on how things are actually practiced out in the wastes. During this time having to repeatedly hit the wall of not being able to pursue the treatment options he knows would resolve the patients issues. Having to wrestle with the fact that despite now working with a team of people that have adapted the best they can to limited supplies that he is still going to have people die in his care - even when he knows the right thing to do.

Back in the Commonwealth, the rest of him probably end up a bit jaded about it, and more aggressive in protecting his personal equipment as a side effect. While with the Followers I think he learns to deal with it much better due to having a support structure or peers. Not only that but rather than having to trial & error it all himself, having a huge amount of improvised tactics being directly taught to him by a bunch of people who have been doing it for years, and have had decades of wastelander tactics being passed around between them.

Having Antyllus around is probably great for the Followers since he's a portable textbook with how well he retains medical facts, and being around them is great for him because he actually learns a lot more than he anticipates. Turns out, having coworkers & peers to share information with is great!

[mourning-again-in-america]

this surely has been written about but idk where

one of the big things software does at my grocery store job is it allows a delocalization of policy controls

if I need to clear an item off the current order so I can start afresh, because it doesn't end in a purchase, I need to call for a manager, who has a key card to permit this

I assume back in the day receipts had a notation for these sorts of things that you needed to store in your register likely with a stamp or initialization of approval, but a manager could shout an adhoc override of the override and you would note it and all could proceed

but these ad hoc policy changes based on the needs of the moment are incredibly important and so much of the infrastructure has been baked into an always correct, always networked computer

the computer cannot be trusted to always be correct and its errors are sharp and irrecoverable without drastic action that often takes hours, if not days.

on the one hand, private equity hollowing out enterprise software (of which POSs are an epitome) is a great fear of mine and I think there's good arguments that this should be treated as a national security crisis for CISSA to issue legally binding guidance on but that might just be that "national security" is the best way to get the govt involved where it shouldn't be

on the other hand, one of the few good results of the FAANG layoffs is the making more likely of greater diffusion of proper software architecture and testing, such as how to build a system that lets you mock the terminals as state machines & experiment with worst-case scenarios. but will it happen?

[shindahime]

NPC: Kiyohime

Name: Adhoc 56

Alias: Kiyohime Chaalaak

Verse: Main Story

Race/Species: Experiment, descendant of Mortau

Age: complicated, a test tube baby born as a teen around 14

Sexuality: straight

Gender/Pronouns: female, she/her

Eye color: pinkish red

Hair: black

Height: 5'5"

Weight: 132 Ibs

Body type: stick

Skin color: almond

Background: A splice using the DNA of Damian Castelleve and an artificial rakshesamat, Hanako.

She was created by Krisha in a laboratory, and on her first mission outside of it, she died.

Having preserved her soul, Krisha remade her body and kept her within her laboratory as a bodyguard for a project she deemed more important.

[valianttimetravelcowboy]

Selecting and Configuring Inference Engines for LLMs

There are many optimization techniques developed to mitigate the inefficiencies that occur in the different stages of the inference process. It is difficult to scale the inference at scale with vanilla transformer/ techniques. Inference engines wrap up the optimizations into one package and eases us in the inference process.

For a very small set of adhoc testing, or quick reference we can use the vanilla transformer code to do the inference.

The landscape of inference engines is quickly evolving, as we have multiple choices, it is important to test and short list the best of best for specific use cases. Below, are some inference engines experiments which we made and the reasons we found out why it worked for our case.

For our fine tuned Vicuna-7B model, we have tried

TGI 

vLLM

Aphrodite 

Optimum-Nvidia

PowerInfer

LLAMACPP

Ctranslate2

We went through the github page and its quick start guide to setup these engines, PowerInfer, LlaamaCPP, Ctranslate2 are not very flexible and do not support many optimization techniques like continuous batching, paged attention and held sub-par performance when compared to other mentioned engines.

To obtain higher throughput the inference engine/server should maximize the memory and compute capabilities and both client and server must work in a parallel/ asynchronous way of serving requests to keep the server always in work. As mentioned earlier, without help of optimization techniques like PagedAttention, Flash Attention, Continuous batching it will always lead to suboptimal performance.

TGI, vLLM and Aphrodite are more suitable candidates in this regard and by doing multiple experiments stated below, we found the optimal configuration to squeeze the maximum performance out of the inference. Techniques like Continuous batching and paged attention are enabled by default, speculative decoding needs to be enabled manually in the inference engine for the below tests.

[davidfegan]

VisionOS App Development Company

VisionOS App Development Services by Agicent

We’ve started learning and honing our skills on VisionOS from the day it was launched in 2023 and now when the device is actually here, we are getting overwhelming requirements for our VisionOS App development services and we offer a complete spectrum of services which are useful for all sizes of projects and startups.

VisionOS App Discovery Session & Consulting Service

In this step, we understand your product vision and the market you want to cater. We gather all your requirements (feature list, use-case, goal, monetization methods and goals, integrations, future vision etc) and consult you on the best features for the MVP or for full product, and also do a competitor analysis to let you know the gaps in the market and propose you the best possible solution. We also lay out a scope of the work and provide you either a fixed price estimation for the VisionOS App development or offer you a dev team on month-on-month basis with these pricing plans.

You can book a Free VisionOS App Discovery Session from here.

VisionOS Apps Design, Wireframes, Prototyping Service

In this step, we convert your feature list into visual design and wireframes. This is the most crucial step among all others as whatever we are going to launch in the market is visualized and finalized here. We closely coordinate with you at this stage, figure out what kind of target market we have and what type of design would they like, and then create the design and simulate that like a clickable prototype or a demo video like this example.

We send these design visualizations for your feedback and approval and do as many iterations as you want and once approved we proceed towards the actual development.

Tech Architecture and Coding Phase: Agile Sprints

Once design is approved, we create the tech architecture to achieve what we have visualized in terms of the design and functionality. And the next step is coding the VisionOS App using SwiftUI, ARKit, Unity, Xcode, ComposerPro tech stacks as well as backend technologies like Node.js, MongoDB or likes.

We create the tech architecture keeping a larger future vision in mind so the MVP VisionOS App we develop today assuming for a small amount of users, should be scaled easily and quickly to cater millions of the users and more advanced features and also leave a lot of room for future integrations with different technologies. Usually our CTO and Engineering leads do the architecture job.

The whole project is broken down into small feature bunches and then they Weekly Agile Sprints are schedule to achieve those features week by week. At every weekend a progressive Adhoc VisionOS App build is released for testers and clients for the UAT. Any bugs or enhancements are noted down and added with the next week’s dev sprint and the build is shipped to either live or test server depending upon your priorities.

Adhoc Distribution and Final go-live

During the development phase, the visionOS App is distributed across a private network (of clients, early users/ testers, dev teams) as an Adhoc build that we create using Apple’s guidelines and protocols on its iTunes connect ecosystem integrated with the Xcode and other tech stacks associated with the VisionOS App Development.

The final App store submission is done when the Dev cycle is complete and you give us a go ahead to go live. We do the whole job for you.

The whole solution is also ported onto the live cloud server and infrastructure using our DevOps experts.

VisionOS App Maintenance, Enhancements, Upkeep

Once the first version goes live, you can either switch to the maintenance phase for the upkeep of the VisionOS App or can go about launched further features for enhancements. Our Dev and maintenance plans starts from as low as $ 2900 mo and sometimes even lesser if you only need under 100 hours of maintenance a month.

Like advanced mobile apps, VisionOS Apps also utilizes various third party APIs from user authentication to several other features like integration with maps, payment gateways, with other apps and backend and all such APIs launch new updates very frequently and hence the VisionOS app will have to be updated accordingly. Also the VisionOS itself is in its nascent stage right now and we can expect atleast 10 major or minor OS upgrades this year and for which a regular support & maintenance service will be required.

By offer Development, Design, Marketing, Maintenance, Porting services we make ourselves as you one stop VisionOS App Development Company.

VisionPro App Porting Services

Here we work to make your existing web app or mobile app to be absolutely compatible and oriented towards the new VisionPro Devices and VisionOS Operating system. You can leverage your existing product and userbase and scale them for VisionOS VisionPro device.

We’ll consult you in identifying which features can be ported onto VisionOS as is and which ones need to be made cmpatible and adaptable to the visionOS unique spatial features.

In most of the existing mobile apps, voice gesture commands and eye commands will be added as a go-to features when it comes to porting on to the visionOS and then more options can be added as the app grows.

VisionPro App Marketing Services

We render our inhouse marketing and sales expertise, tools and workflows for our clients and craft highly efficient and performance-oriented performance marketing campaigns to promote your VisionPro App.

This can include (but not limited to) – Paid ad campaigns to install VisionOS Apps across big outlets like Google, Meta/ FB/ Insta, Linkedin; organic SEO and organic campaigns, Organic and paid PR campaigns, Video content marketing, influencer marketing, Opinion leadership influenced market, Cross App integration promotion and so on.

You tell us your monthly App marketing budget and goal and we’ll craft and run and optimize the best campaign inside that.

Benefits of creating VisionOS Apps for Startups and Business

Clear Competitive Edge: The early mover advantage

It’s a very new device and have only started being sold in some parts of the US only. Anyone moving first for this device is definitely going to get a lot of advantage in terms of targeting the niche and comparatively upscale user-base.

Even the existing Apps that will scale for VisionPro Device exploiting its AR/ VR spatial capabilities are going to offer enhanced experience to its existing user base and gain more customer loyalty and branding.

A new world of opportunity to Innovative

For the same reasons as stated above, its spatial computing capabilities have opened a whole new world of amazing innovation opportunities. We’ve listed below some of the possible innovative use cases for various industries on this page itself, and we believe that there will be millions of amazing use cases out there that can solve the current world problems in much better ways than what is being done by the current smartphone device and apps.

Integrating the VisionOS apps with different devices will offer great possibility to further innovate as well where several interconnected devices sharing and exchanging data will proide more seamless convenient life to the user especially for healthcare, home automation, and business usage.

Unique and Immersive Experience

Vision Pro’s unique spatial computing, tracking and depth perception allow for highly realistic and interactive experiences in augmented reality (AR) and Virtual reality. Users can experience and manipulate virtual objects in a natural human way and that will create a sense of real presence and break down the barrier between the physical and virtual digital world.

Any app utilizing these spatial immersive capabilities are going to be used more and more by the users compared to regular mobile or web apps and therefore launching an app on VisionOS gives you a more loyal and consistently engaged user-base.

Better interactive Storytelling

You can tell your story in more interactive and appealing way when it looks and feel closer to the reality and that is exactly what Visionpro device offers to its users. Businesses as well as creators can create and tell immersive mixed reality stories that can actually engage users for a longer span than just scrolling back in few seconds.

A historical content creator can create virtual historical battles that you can see happening in front of your eyes, or or viewing ancient battles unfold right before your eyes. Or a virtual story showcasing you the world of dinosaurs as a moving and sounding reality.

Same goes for product visualization as we’ve discussed the same concept in details below in Ecommerce Use-case. You can showcase and appeal your product with a realistic experience, creation of immersive demos and free trials can help marketers win the consumer’s confidence to a higher degree than what you are able to do with the old technologies.

Story is everything, and VisionOS allows you to tell your story in the best way possible so far in the history of the mankind.

VisionOS App development is not complex

Creating mixed reality Apps have always been a complex and typical exercise compared to the conventional software development, especially because of the demand of creating interactive virtual reality UI and UX. However, VisionOS has already done majority of the heavy lifting and if developers are familiar with Apple iOS development and Arkit (which our developers are) then creating VisionOS Apps using the same skill sets becomes really easy.

Its juts a transition of the device and the change of UI, while rest of the technologies will be as same as iOS developers have been using for the last few years.

Process of Creating VisonPro VisionOS Apps and the required Tools

Understanding the Vision Pro Ecosystem and its features

At the heart of the Vision Pro experience is the blend of virtual reality (VR) and augmented reality (AR), powered by Apple’s cutting-edge M2 chip and a specialized R1 chip. These components work in harmony to deliver unparalleled performance and immersive experiences, tracking your movements and rendering captivating virtual environments.

Understand its most important and unique features, such as:

Eye, Hands, and Voice based gesture commands:So whichever VisionPro app idea that you are contemplating to create should completely exploit these cool features.

Virtual Avatars and 3D Facetime: Virtual avatar in VisionPro universe are going to more realistic and so as the video calls. We also think of a scenario where an AI avatar of yours takes a meeting on your behalf while you physically take another meeting and the possibilities are endless.

Immersive-ness Control:VisionPro users can increase or decrease the level of immersiveness as per their choice, so your App should be compliant to the same.

Transparent Display: As VisionPro is a mixed reality spatial device, the display is actually transparent as it goes hand in hand with the reality. So your UI/UX design must adhere to this fact and in most of the cases a minimal design will turn out to be the best design because everything else will be taken care of by the real world.

02. Getting Started with visionOS App Development

The gateway to creating apps for Vision Pro is visionOS, Apple’s bespoke operating system tailored for spatial computing. This environment is your canvas, allowing you to merge digital creations with the physical world seamlessly. To set sail on this development journey, you’ll need a Mac running macOS Monterey or newer, the latest version of Xcode, and the Vision Pro developer kit. At Agicent’s VisionOS App Development Company, we’ve all the required infrastructure, team, testing devices and some more. You just have to tell us about your project, and we take care of the rest.

03. Ideation of VisionPro VisionOS App

An entrepreneur or startup or a brand should explore all the possibilities a spatial VisionOS App can achieve on this device. Do a market analysis, competitive analysis, go back to the history where web apps exploited mobile capabilities and a new market was emerged, so similarly think of what additional capabilities mobile apps can offer if they are ported onto visionPro devices.

We think of scenarios in the industries like healthcare where preventive healthcare and telemedicine apps can be created for VisionOS with spatial capabilities, or in an industry where there are plenty of machines and a VisionPro Maintenance App can tell the supervisor about health, maintenance schedule, warranty of the machines just by looking at them, or think of a real estate app where you just wear your visionpro device and see which of the properties in front of you are up for sale or rent and so on.

It is always beneficial to have a industry or subject matter expert on board while ideating for an app for that particular industry, however there are some low hanging fruits that anyone can achieve simply by scaling the existing apps with the spatial mixed reality features for the visionpro device.

We as a VisionOS App Development Company provide you consulting service even before development in figuring out the right features, UI/ UX and target userbase for your VisionOS App idea.

Source: https://visionosappdevelopmentcompany.com/

[blockchainss]

Smart Contracts Security Program - 101 Blockchains

This course is specifically designed for developers and engineers who are interested in learning about the critical vulnerabilities and security risks associated with smart contract development. It covers various topics including integer overflow, precision loss, reentrancy attacks, and advanced attacks like flash loan attacks. Additionally, the course provides in-depth modules on important subjects such as smart contract security testing and auditing, safe transfer of ether, and vulnerabilities related to NFTs. Furthermore, learners will have the opportunity to gain hands-on experience with smart contract vulnerabilities and attacks.

Learn More About : - Fintech Certification

The author of this course, Gimer Cervera, is a Blockchain Engineer who has been developing and auditing smart contracts since 2018. He holds a Ph.D. in Computer Science from Carleton University in Ottawa, Canada, with a focus on distributed systems and security attacks on Mobile AdHoc Networks. In the Blockchain industry, he has worked as a consultant, developer, and engineer for various companies. Additionally, Gimer has over 15 years of experience as an instructor and university professor in Mexico. He is the owner of the site DappDojo and has a true passion for Blockchain technology.

The author highly recommends taking the Certified Blockchain Professional, which provides a comprehensive understanding of the subject and strikes the right balance between technical content and its practical applications in business. The knowledge gained from this course will greatly enhance one's career.

The smart contracts security course includes video lectures for each lesson within the modules. These lectures feature real-world examples of smart contract implementations and provide practical insights from industry experts. Learners will also find demonstrations on blockchain smart contract security and learn how to use tools and frameworks to identify potential pitfalls in smart contract security. It's worth noting that this course does not have any prerequisites, making it accessible to all interested individuals.

[this-week-in-rust]

This Week in Rust 481

Hello and welcome to another issue of This Week in Rust! Rust is a programming language empowering everyone to build reliable and efficient software. This is a weekly summary of its progress and community. Want something mentioned? Tag us at @ThisWeekInRust on Twitter or @ThisWeekinRust on mastodon.social, or send us a pull request. Want to get involved? We love contributions.

This Week in Rust is openly developed on GitHub. If you find any errors in this week's issue, please submit a PR.

Updates from Rust Community

Official

Announcing Rustup 1.25.2

Foundation

Member Spotlight: AdaCore

FOSDEM 2023

[video] Building an actor library for Quickwit's indexing pipeline

[video] Building a distributed search engine with tantivy

[video] Aurae: Distributed Runtime

[video] BastionLab, a Rust open-source privacy framework for confidential data science collaboration

[video] Neovim and rust-analyzer are best friends

[video] A Rusty CHERI - The path to hardware capabilities in Rust

[video] Slint: Are we GUI yet?

[video] Rust API Design Learnings

[video] A deep dive inside the Rust frontend for GCC

[video] Merging process of the rust compiler

[video] Let's write Snake game!

[video] Glidesort

[video] How Pydantic V2 leverages Rust's Superpowers

[video] Scalable graph algorithms in Rust (and Python)

[video] Using Rust for your network management tools!

[video] Backward and forward compatibility for security features

[video] atuin: magical shell history with Rust

[video] A Rust-Based, modular Unikernel for MicroVMs

Newsletters

This Month in Rust OSDev: January 2023

The first issue of Rust Magazine has been published 🎉🎉

Project/Tooling Updates

Release Engineering Is Exhausting So Here's cargo-dist

rust-analyzer changelog #167

Glidesort, my stable adaptive quicksort/mergesort hybrid sorting algorithm

Fornjot (code-first CAD in Rust) - Weekly Release - Ostensibly Quiet

derive-adhoc: "derive by example", an ergonomic replacement for (some) proc macros

Lemmy release 0.17.0 - A link aggregator for the Fediverse

Arti 1.1.1 is released: Groundwork for onion services

SeaORM 0.11.0 - 🐚 An async & dynamic ORM for Rust

Observations/Thoughts

Async trait send bounds, part 1: intro

Speeding up Rust semver-checking by over 2000x

Announcing Masonry 0.1, and my vision for Rust UI

Rust Is Beyond Object-Oriented, Part 2: Polymorphism

[video] Rust Malaysia - The journey to rust from a student

Improving incremental test times in Rust

Using HTML as a compile target

Tauri vs Iced vs egui: Rust GUI framework performance comparison

Improving Rust compile times to enable adoption of memory safety

[audio] Cloudflare with Adam Chalmers

Rust Walkthroughs

Building a Rust parser using Pest and PEG

Rustler - Using Rust crates in Elixir

LifetimeKata: Exercises to learn how to use lifetimes

Exploring Rust for Vulkan drivers, part 1

Rustproofing Linux (Part 1/4 Leaking Addresses)

STM32F4 Embedded Rust at the PAC: svd2rust

Miscellaneous

My Reaction to Dr. Stroustrup's Recent Memory Safety Comments

This Is the Kind of Rust the Automotive Industry Needs

Crate of the Week

This week's crate is envious, a serde-based deserializer from environment variables.

Thanks to musicmatze for the suggestion!

Please submit your suggestions and votes for next week!

Call for Participation

Always wanted to contribute to open-source projects but did not know where to start? Every week we highlight some tasks from the Rust community for you to pick and get started!

Some of these tasks may also have mentors available, visit the task page for more information.

this-week-in-rust - Make dark mode more accessible

Ockam - 'ockam tcp-connection create' should return the tcp-connection ID

Ockam - 'ockam node stop' should output a message when exiting successfully

comprehensive-rust - We now support translations!

comprehensive-rust - Extract text more carefully in mdbook-xgettext

If you are a Rust project owner and are looking for contributors, please submit tasks here.

Updates from the Rust Project

350 pull requests were merged in the last week

retry opening proc-macro DLLs a few times on Windows

autotrait bounds on dyn-safe trait methods

do not depend on Generator trait when deducing closure signature

parse and recover from type ascription in patterns

recover _ as .. in field pattern

recover form missing expression in for loop

recover from lifetimes with default lifetimes in generic args

don't generate unecessary &&self.field in deriving Debug

emit warnings on unused parens in index expressions

erase regions before doing uninhabited check in borrowck

extend -Z print-type-sizes to distinguish generator upvars+locals from "normal" fields

fix invalid float literal suggestions when recovering an integer

fix suggestion for coercing Option<&String> to Option<&str>

fix syntax in -Zunpretty-expanded output for derived PartialEq

fixing confusion between mod and remainder

implement unsizing in the new trait solver

don't point at nonexisting code beyond EOF when warning about delims

improve diagnostic for missing space in range pattern

improve panic message for slice windows and chunks

improve pretty-printing of HirIdValidator errors

make unaligned_reference a hard error

make const/fn return params more suggestable

make the "extra if in let...else block" hint a suggestion

provide structured suggestion for binding needing type on E0594

refine error spans for "The trait bound T: Trait is not satisfied" when passing literal structs/tuples

remove confusing 'while checking' note from opaque future type mismatches

sort Generator print-type-sizes according to their yield points

suggest move in nested closure when appropriate

suggest std::ptr::null if literal 0 is given to a raw pointer function argument

suggest {var:?} when finding {?:var} in inline format strings

suggest adding a return type for async functions

intern external constraints in new solver

optimize fold_ty

do not deaggregate MIR

adapt SROA MIR opt for aggregated MIR

test drop_tracking_mir before querying generator

track bound types like bound regions

futures: poll Select futures without moving them

cargo: add partial support for SSH known hosts markers

cargo: config: deny CARGO_HOME in env table

cargo: do not error for auth-required: true without -Z sparse-registry

cargo: handle .cargo-ok being truncated

cargo: make cargo install report needed features

cargo: verify source before recompile

rustfmt: prevent shorthand init for tuple struct

rustfmt: lists doc comments

clippy: needless_lifetimes: lint local macros

clippy: unused_io_amount: lint with is_ok and is_err

clippy: wildcard_enum_match_arm lint takes the enum origin into account

clippy: add extra_unused_type_parameters lint

clippy: add machine applicable suggestion for needless_lifetimes

clippy: don't depend on FormatArgsExpn in ManualAssert

clippy: fix version declared for semicolon_inside_block and semicolon_outside…

clippy: mark uninlined_format_args as pedantic

rust-analyzer: add more basic issue templates with auto category labeling

rust-analyzer: expand docs section on Visual Studio to mention all three available extensions

rust-analyzer: remove support for 1.58 proc-macro abi

rust-analyzer: fix negative trait bound in outline view (#14044)

rust-analyzer: consider relative offset to fake ident token in expansion for completion

rust-analyzer: don't panic on broken syntax trees in adjustment inlay hints

rust-analyzer: don't render fieldless discriminant inlay hints for datacarrying enums

rust-analyzer: support non-ascii characters in case conversion

rust-analyzer: unsize cast array only on pointer type

rust-analyzer: implement proc-macro-api versioning

rust-analyzer: record method resolution for remaining operator expressions

rust-analyzer: reuse fetching target data layout from rustc function

rust-analyzer: support computing layout of RPIT

rust-analyzer: support generic function in generate_function assist

rust-analyzer: support sysroot library source being defined inside the workspace

Rust Compiler Performance Triage

Much noise in benchmarks this week, which makes it hard to tell what the real improvements were and what they were due to. A query cache change (PR #107667) is part of the story. In addition, much improvement was reaped from the change to not deaggregate MIR (PR #107267). Finally, microoptimizing fold_ty (PR #107627) yielded a small improvement to a broad set of benchmarks.

Triage done by @pnkfelix. Revision range: a64ef7d0..e4dd9edb

Summary:

(instructions:u) mean range count Regressions ❌ (primary) 2.4% [0.3%, 18.8%] 18 Regressions ❌ (secondary) 1.8% [0.2%, 4.1%] 21 Improvements ✅ (primary) -1.0% [-3.2%, -0.3%] 88 Improvements ✅ (secondary) -4.0% [-13.1%, -0.1%] 47 All ❌✅ (primary) -0.4% [-3.2%, 18.8%] 106

3 Regressions, 3 Improvements, 8 Mixed; 3 of them in rollups 41 artifact comparisons made in total

Full report here

Approved RFCs

Changes to Rust follow the Rust RFC (request for comments) process. These are the RFCs that were approved for implementation this week:

No RFCs were approved this week.

Final Comment Period

Every week, the team announces the 'final comment period' for RFCs and key PRs which are reaching a decision. Express your opinions now.

RFCs

No RFCs entered Final Comment Period this week.

Tracking Issues & PRs

[disposition: merge] rework min_choice algorithm of member constraints

[disposition: merge] fix: Unexpected trait bound not satisfied in HRTB and Associated Type

[disposition: merge] Stabilize feature cstr_from_bytes_until_nul

[disposition: merge] rustdoc: remove inconsistently-present sidebar tooltips

[disposition: merge] Relax ordering rules for asm! operands

New and Updated RFCs

[new] recommended-bin-crates field in Cargo.toml

[new] Ref-wrapping

Call for Testing

An important step for RFC implementation is for people to experiment with the implementation and give feedback, especially before stabilization. The following RFCs would benefit from user testing before moving forward:

No RFCs issued a call for testing this week.

If you are a feature implementer and would like your RFC to appear on the above list, add the new call-for-testing label to your RFC along with a comment providing testing instructions and/or guidance on which aspect(s) of the feature need testing.

Upcoming Events

Rusty Events between 2023-02-08 - 2023-03-08 🦀

Virtual

2023-02-08 | Virtual (Boulder, CO, US) | Boulder Elixir and Rust

Monthly Meetup

2023-02-08 | Virtual (Redmond, WA, US; New York, NY, US; San Francisco, CA, US) | Microsoft Reactor Redmond and Microsoft Rector New York and Microsoft Reactor San Francisco

Primeros pasos con Rust: QA y horas de comunidad | New York Mirror | San Francisco Mirror

2023-02-09 | Virtual (Nürnberg, DE) | Rust Nuremberg

Rust Nürnberg online

2023-02-11 | Virtual | Rust GameDev

Rust GameDev Monthly Meetup

2023-02-13 | Virtual (Redmond, WA, US; New York, NY, US; San Francisco, CA, US) | Microsoft Reactor Redmond and Microsoft Rector New York and Microsoft Reactor San Francisco

Primeros pasos con Rust - Escritura de pruebas automatizadas | New York Mirror | San Francisco Mirror

2023-02-14 | Virtual (Berlin, DE) | OpenTechSchool Berlin

Rust Hack and Learn

2023-02-14 | Virtual (Dallas, TX, US) | Dallas Rust

Second Tuesday

2023-02-14 | Virtual (Redmond, WA, US; New York, NY, US; San Francisco, CA, US) | Microsoft Reactor Redmond and Microsoft Rector New York and Microsoft Reactor San Francisco

Primeros pasos con Rust - Creamos un programa de ToDos en la línea de comandos | San Francisco Mirror | New York Mirror

2023-02-14 | Virtual (Saarbrücken, DE) | Rust-Saar

Meetup: 26u16

2023-02-15 | Virtual | MongoDB

Write a Microservice With Rust and MongoDB

2023-02-15 | Virtual (Redmond, WA, US; New York, NY, US; San Francisco, CA, US; São Paulo, BR) | Microsoft Reactor Redmond and Microsoft Rector New York and Microsoft Reactor San Francisco and Microsoft Reactor São Paulo

Primeros pasos con Rust: QA y horas de comunidad | San Francisco Mirror | New York Mirror | São Paulo Mirror

2023-02-15 | Virtual (Vancouver, BC, CA) | Vancouver Rust

Show & Tell: Rust state machines in a file processor

2023-02-16 | Virtual (Stuttgart, DE) | Rust Community Stuttgart

Rust-Meetup

2023-02-21 | Virtual (Washington, DC, US) | Rust DC

Mid-month Rustful

2023-02-23 | Virtual (Charlottesville, VA, US) | Charlottesville Rust Meetup

Tock, a Rust based Embedded Operating System

2023-02-23 | Virtual (Kassel, DE) | Java User Group Hessen

Eine Einführung in Rust (Stefan Baumgartner)

2023-02-23 | Virtual (México City, MX) | Rust MX

Rust: ¿por qué es una opción adecuada para implantar Blockchain?

2023-02-28 | Virtual (Berlin, DE) | Open Tech School Berlin

Rust Hack and Learn

2023-02-28 | Virtual (Cardiff, UK) | Rust and C++ Cardiff

Rust Nation - What we learnt

2023-02-28 | Virtual (Dallas, TX, US) | Dallas Rust

Last Tuesday

2023-02-28 | Virtual (Munich, DE) | Rust Munich

Rust Munich 2023 / 1 - hybrid

2023-03-01 | Virtual (Indianapolis, IN, US) | Indy Rust

Indy.rs - with Social Distancing

2023-03-02 | Virtual (Linz, AT) | Rust Linz

Rust Meetup Linz - 30th Edition

2023-03-07 | Virtual (Buffalo, NY, US) | Buffalo Rust Meetup

First Tuesdays

2023-03-08 | Virtual (Boulder, CO, US) | Boulder Elixir and Rust

Monthly Meetup

Asia

2023-02-14 | Tokyo, JP | Tokyo Rust Meetup

Crafting Command Line Tools With Rust

2023-02-20 | Tel Aviv, IL | Rust TLV

February Edition - Redis and BioCatch talking Rust!

Europe

2023-02-09 | Lille, FR | Rust Lille

Rust Lille #2

2023-02-15 | London, UK | Rust London User Group

Rust Nation Pre-Conference Reception with The Rust Foundation

2023-02-15 | Trondheim, NO | Rust Trondheim

Rust New Year's Resolution Bug Hunt

2023-02-16 | Bordeaux, FR | DedoTalk

#1 DedoTalk 🎙️ : Rust pour un développeur Python

2023-02-16, 2023-02-17 | London, UK | Rust Nation UK

Rust Nation '23

2023-02-18 | London, UK | Rust London User Group

Post-Conference Rust in Enterprise Brunch Hosted at Red Badger

2023-02-21 | Paris, FR | Rust Paris

Rust Paris meetup #56

2023-02-21 | Zurich, CH | Rust Zurich

Practical Cryptography - February Meetup (Registration opens 7 Feb 2023)

2023-02-23 | Copenhagen, DK | Copenhagen Rust Community

Rust metup #33

2023-02-23 | Vienna, AT | Rust Vienna

Rust Meetup Revived with an Exciting Exploration of Ownership!

2023-02-28 | Munich, DE + Virtual | Rust Munich

Rust Munich 2023 / 1 - hybrid

North America

2023-02-09 | Mountain View, CA, US | Mountain View Rust Study Group

Rust Study Group at Hacker Dojo

2023-02-09 | New York, NY, US | Rust NYC

A Night of Interop: Rust in React Native & Rust in Golang (two talks)

2023-02-13 | Minneapolis, MN, US | Minneapolis Rust Meetup

Happy Hour and Beginner Embedded Rust Hacking Session (#3!)

2023-02-21 | San Francisco, CA, US | San Francisco Rust Study Group

Rust Hacking in Person

2023-02-23 | Lehi, UT, US | Utah Rust

Upcoming Event

Oceania

2023-02-23 | Brisbane, QLD, AU | Rust Brisbane

February Meetup

2023-02-28 | Canberra, ACT, AU | Canberra Rust User Group

February Meetup

2023-03-01 | Sydney, NSW, AU | Rust Sydney

🦀 Lightning Talks - We are back!

South America

2023-02-22 | Montevideo, UY | Rust Meetup Uruguay

Hands on: Lifetimes

If you are running a Rust event please add it to the calendar to get it mentioned here. Please remember to add a link to the event too. Email the Rust Community Team for access.

Jobs

Please see the latest Who's Hiring thread on r/rust

Quote of the Week

It's been 7.5 years since #27060 was reported, but the problem is finally fixed for good. :‍)

– Ralf Jung on github

Thanks to scottmcm for the suggestion!

Please submit quotes and vote for next week!

This Week in Rust is edited by: nellshamrell, llogiq, cdmistman, ericseppanen, extrawurst, andrewpollack, U007D, kolharsam, joelmarcey, mariannegoldin, bennyvasquez.

Email list hosting is sponsored by The Rust Foundation

Discuss on r/rust

[mourning-again-in-america]

my shitpost theory of webdev is that every sufficiently advanced client/server library wants to be written in a Lisp, demonstrated by the one good decision Paul Graham ever made

also, having seen a very small view of things, it seems like languages that aren't lispy from the start like Ruby often develop similar traits to macros with kludges often arising from their dissimilarity from true macros (which may have only started to exist in Racket? Not sure)

Python has decorators in flask and I think fastapi, not sure what the hell Django's doing, it looks like it's wearing Python as a skinsuit

Haskell has a piss-poor "actual macro" system but most of the benefit of the advanced type system is the ability to replicate macro like features, like dynamic dispatch + sealed objects (DataKinds and closed type families) and complex adhoc inheritance-like behaviors (the deriving mechanism, where a library author writes some instances of a trait for a bunch of base objects (String, Int, etc.) and some instances for combinations of those objects) which appear to be not unlike C++ templates

These additions are used heavily in Haskell's best webshit library family, where you specify your routes wholly in the types and you get automatic generation of client functions (which, when called, act as if they hit the HTTP route, handy for testing without testing the networking stack) whenever you add a new route to your server and that's not even getting into property testing in Haskell, which imo is the true argument in favor of Haskell if you're not a compiler dev or otherwise oddly situated

there have been, no doubt, countless "advances" which have served only to delay or destroy progression of the development of software systems. but i should be grateful, for the following reads mostly like nonsense to me

[aworldofpsychos]

Neuer Abschnitt

[webomates]

In the software testing arena, a commonly asked question is whether Exploratory testing is same as the Ad Hoc Testing? They do have some overlap which causes confusion, but in reality, they are quite different. 

Know More: https://www.webomates.com/blog/manual-testing/ad-hoc-testing-vs-exploratory-testing/

[shindahime]

NPC: Penelope

Name: Adhoc 55

Alias: Penelope Chaalaak

Verse: Main Story

Race/Species: Experiment, descendant of Mortau

Age: complicated, a test tube baby born as a teen around 14

Sexuality: straight

Gender/Pronouns: female, she/her

Eye color: bright yellow

Hair: brown

Height: 5'3"

Weight: 115 Ibs

Body type: stick

Skin color: Mahogany

Background: A splice using the DNA of a far away country's Queen and Beauregard Castelleve.

She was created by Krisha in a laboratory, and on her first mission outside of it… She was killed.

Having preserved her soul, Krisha remade her body and kept her within her laboratory as a bodyguard for a project she deemed more important…

[fandroidrobotheadcanons]

ik that this is a rlly popular idea in the fandroid fandom already, but i feel like frogbot def has a spring w/ a suction cup on the end to move around instead of a wheel

[wootzietoozee]

EVERYTHING IS FINE!

[bugsinspace]

fine l bite. what is fandroid

i giggled like a little idiot reading this ask. OK SO. uh. fandroid is a youtuber! a group of youtubers actually. just a couple guys acting. and the characters they play are robots! fandroid started out as just one guy running a kids' yt channel but after a hiatus of ~3 years he came back with what's essentially a reboot. they play video games and stuff. the original fandroid's lore was very few and far between- basically there's these robotics companies, ADHOC and QUALIA. Fandroid and the majority of the characters we see were built by ADHOC. and ADHOC... kind of sucks!!! shady practices and all that. Fandroid and his fellow robots were NOT TREATED WELL IN THE SLIGHTEST! he was locked in one room for his Entire life, except for a few times where he was taken to other places to be tested and experimented on. yikes. he was SUPPOSED to be all alone, until one day Melody- another character- broke in through the vents and basically said "this guy is my friend now." Melody is a runaway robot from QUALIA. the kind of robot she is, a series of toys called Drone Buddies, is made to imprint on one specific human kid and be their bff. melody is broken. she chose fandroid instead! being a product from ADHOC's rival company, ofc ppl didn't like her. little menace to everyone INCLUDING fandroid (she threw a toaster at his head at one point) but its ok theyre fine im sure this friendship is healthy and normal! there's also a few prototypes, the three main ones are Beep-0, the first prototype, Frogbot, the silliest little guy around, and Fandrew, the one i'm obsessed with. i hate him. i need him to be okay. he's insane.anyway. some big Event happened leaving all the humans at adhoc Dead. sad! well there's other companies. around this time Fandroid was put into a kind of. stasis? hibernation? he was asleep(deactivated?) for a LOOOOOONG time. from 2020 to around the end of this year's january. but he's back! he's okay! i'm sure this won't do anything negative for his mental health!!! so things are okayish for a while.

and then robots start going missing.

Business Bot, a rather obscure character no one really talked about much anyway, was dismantled. Panic spread throughout the remaining robots at the facility.

Enter 404. A new character who wasn't in the original Fandroid. An error message given life, he now seeks a physical form, tearing off pieces of other robots to build onto himself. He got Business Bot, a little bit of Frogbot and is now going after the others...

However, he sucks at this. He's sooooo cringefail i need to shove him into a locker. he's the worst. people want to kiss him. people want him and beepo to kiss. robot yaoi.

so thats what ive been obsessing over for the past few months. hi twip