-
-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Length of frames #1
Comments
Does Coq have a bounded integer library? I'm a bit reluctant to depend on external packages. |
One way to encode bounded integers in Coq is using subset types However, many people would suggest reconsidering the options before using that because reasoning about dependent types (for example, when doing unification, etc.) in Coq can be painful... |
Also, considering that |
I think that Sigma type encoding Re: 16M: maybe we can also define 16K and 16M to be some large enough unknown constants. |
|
Well, our client or server can always fix the bound to exactly 16384, the default value. |
If we treat |
But anyway, I do not have a strong opinion on this. If you decided to use the binary format |
I believe that is the case. We only have to make sure proper bound-checking is enforced with respect to some "reasonable" constants. |
This value can be modified by SETTINGS frames. I don't think it's proper to make it opaque. |
You will want to say something like, for all values we can give to the settings, some properties hold. And reasoning about the setting should not rely on it being a particular value. Therefore, the values of settings remain abstract all the time and there is no concrete number that we need to worry about. I am not suggesting to keep using |
And although I have heard a lot of arguments against using sigma types, I would actually be interested to see how they would play out here... |
To be concrete, what would a running checker look like? |
I think 16M is a reasonable constant limit here. The static bound-checking tells if the frame can be valid in any context, and the runtime checking decides whether this frame is valid under current context. |
Is there a reason not to use bounded integers for the lengths?
The text was updated successfully, but these errors were encountered: