Is there an @inbounds equivalent for type assertions? That is allow the compiler to aggressively compile a specialization based on a type assertion that is unsafe if the type is not correct?

This occurred to me as related to your question: [image] Unreasonable slow speed in numerical integration Note also that your argument-type and return-type declarations don’t impact performance and it is probably clearer to omit them. See also: Be aware of when Julia avoids specializing

You can assert a type of a value or expression. The compiler knows that this means the expression is either of that type or raises an error. There’s no way to do this unsafely.

@inbounds equivalent for type assertions

General Usage

jd-foster November 8, 2022, 11:09am 2

This occurred to me as related to your question:

Topic		Replies	Views
How to omit type assertion from compiled output General Usage question	8	327	April 30, 2023
Feature request: type assertion for compiler-known type General Usage	21	1249	April 13, 2018
Benchmarking surprises with type assertions General Usage benchmark	10	437	March 18, 2024
Should Julia raise errors for illegal return type annotation? Internals & Design	6	2677	September 4, 2021
How to assert type after if-else General Usage	5	789	October 2, 2017

@inbounds equivalent for type assertions

Related topics