It means `makeBatchOfToast()` is available from toasterOS1.0. So if you are running toasterOS0.5 you are out of luck.
If you are targeting toasterOS1.0, `@backDeployed` will ensure that the function that is copied to your binary is used. For toasterOS2.0 and above, the function provided by the linked framework will be used.
Well kite could be written as keit to match the pronunciation :)
For most non-native speakers, the backtracking of silent `e` is more confusing. It does not help in case of `sake` vs `saké` where most people do not add the acute mark and use context for disambiguation.
Location: Sydney, Australia
Remote: Yes
Willing to relocate: After Covid
Technologies: Backend, Embedded, Golang, C/C++, Python, Swift, C#, Java, AWS, GCP, Terraform
Résumé/CV: https://www.linkedin.com/in/surajbarkale/
Email: suraj@barkale.com
Notes: I am a generalist engineer who is looking for next challenge to expand my knowledge. I have worked across various domains and I am flexible with technology. My recent projects are DolbyON app and dolby.io website.
It is possible to use Swift on audio thread. You have to be careful not to use any reference counted (i.e. class) objects. If you do need to perform allocations (e.g. creating CMSampleBuffer instances), use a custom allocator.
I had someone on the Swift compiler team tell me unequivocally that they make no real time guarantees. Unless you can point to somewhere in the language documentation that the runtime is guaranteed not to ever do X, then I would not assume that you could. (me: former Apple CoreAudio engineer)
If you want to call rust from Swift, it should be easy. I work with C libraries and it easy to interface with module maps. However, with objective C the interoperability is trivial. As long as you pay attention to retain cycles, you can hold reference and call objc methods directly. That said, please make sure your framework can be imported into Swift properly. As most of the users will be using Swift.
Yes, I've seen examples of calling Rust from Swift, and I do plan to support that. This particular thing is about calling macOS platform functions from Rust code. Projects either call Objective-C API's from native Rust code using the dynamic invocation mechanism (which I think is slow and code-bloaty but want to measure more carefully), or they use the "cc" crate to include Objective-C code (and then generally use C ABI calls from Rust code into that). I've never seen Rust code that compiles Swift from a "cargo build" but of course would love to be proven wrong.
When I was a rookie programmer 12 years ago, I was assigned a task to optimise a routine. It took current vehicle speed as input, performed integration and calculated total distance traveled. I made a mistake that was let through code review and was caught by an automated test. My calculations were off by 1% which accumulated to a larger amount in 10 minutes. After that incident we never had another bug for 5 years in that module. Does this make the tests invalid? Our does this improve confidence in our code?
I can't speak for Telugu however, [Devanagari](https://en.wikipedia.org/wiki/Devanagari) is very similar and used throughout northern India. Each vowel and consonant is considered as a separate entity. Each consonant has a pure form and a combined form with every consonant. There are also combinations of two or more consonants that can also be combined with each vowel!
For learning, you just learn the sounds separately for each vowel and consonant. So you can read & pronounce anything written in Devanagari script but not understand it if its a different language :)
I haven't used Flynn, however I am using terraform. Main purpose is to completely automate AWS configuration so we can bring up entire site in CI. This makes it really easy to have staging and production deployed from CI.
