Isn't this solving a subproblem of the overall issue of uncompressed tool call polluting context?
Furthermore, this could be compressed even further with a dynamic legend of every UUID in the context. So UUID@Bravo and UUID@Delta would be the actual symbols in the context but dynamically replaced when calling tools.
Regarding AVX: could rust be compiled with different symbols that target different x64 instruction sets, then at runtime choose the symbol set that is the more performant for that architecture?
> First Revision - Completed with minimal human contribution (auto-accept mode)
>
> Second Revision - Planned with increased human-in-the-loop involvement
At least 'minimal human contribution' in the first revision. So scan read it as it revised the book.
I do find it amusing to think that people might just ask an AI to summarize the book instead of actually reading it. Maybe even 'review' it as well.
Newton Raphson could be used to calculate a reciprocal. (in a bit width larger than 8). If starting from a good reciprocal approximation, convergence to bit accurate reciprocal should not take many iterations. Then multiply the reciprocal with the numerator to perform the divide
I worked on an automotive FMCW LiDAR that didn't quite make it to market. Cool technology but it was difficult to scale the cost down, which is pretty important for automotive. Margins are very low in that market
It's also, if not more so, a factor of transistor voltage. 1.1V transistors are less prone to upset events than 0.7V. It's possible (assumption, here) that some 3+ volt circuits are still used for critical components of the system
It's a perfect time for Matt Colville's MCDM RPG to be announced. It's on backerkit and people are clearly eager for something different. The crowdfunding is at 4x funding and climbing
If there _was_ a good reason to fire Sam, and the board had appropriately and clearly communicated their decision, I think less of the staff would have signed a the petition to walk. From the public's perspective, and probably most rank and file employees, this decision came from left field and had no logic behind it. The waffling and back peddling that followed certainly didn't help perception
nod.ai was just acquired by AMD for a chunk of money. I expect they hope to find a similar exit once they can show an end-to-end product: Take a model written in Pytorch, upcast it to mojo, and put it through their unified compiler stack to accelerate on <hardware>
Furthermore, this could be compressed even further with a dynamic legend of every UUID in the context. So UUID@Bravo and UUID@Delta would be the actual symbols in the context but dynamically replaced when calling tools.