almost-one-liner (though it will give you the full model):
import z3; z3.solve([z3.Sum([ord(a) == z3.Int(f"k{i}") for i, a in enumerate(r[0])]) == r[1] for r in [("bbababbabb", 7), ("baaababaaa", 5), ("baaabbbaba", 3), ("bbaaabbaaa", z3.Int("x"))]])
The AfD had a large secret meeting with right extremists discussing "re-migration" policy this last November, and many members have close ties to Neo-Nazis.
Hi lou, I'm a contributor to Storm and will continue to work on it in my upcoming PhD position. The bottom line is that there are some things you can only do in PRISM and there are more things you can only do in Storm, but if you can do it in both, Storm is usually much faster (see QComp: https://qcomp.org/).
PRISM has better documentation. Storm has recently recieved a grant that will help improve its user interface and applicabilty.
I would like to hear from you what ideas and applications you have for using PMC! :)
> Another common theme is that while Julia is great at composition, it's not clear what's expected to work and what isn't, because the interfaces are informal and not checked.
This is THE huge issue when combined with the other variables:
- you often have hundreds of depedencies that interlock
- you often have dependencies that work with multiple packages, and they will often pull them all into your tree (there are sometimes "bridge packages" written, but that is O(n^2) in the number of packages)
- many maintainers do not care about good versioning practices, because they are not enforced, and it is not their problem when they break a bajillion other packages
- many people writing Julia code are not software developers. this is great! but they usually don't look at what their testing coverage looks like. often the CI always fails on a package and it's ignored.
Would Julia only allow multiple dispatch as a link between those packages, the situation would look a little better. But often the packages also talk through simple accesses of values like `X.someproperty`. I've seen situations where maintainers would add and remove these properties and break their own other libraries. Better "enforcement" of these types of things - however that would look like - would be a huge improvement for the time sink that is maintaining a Julia package.
The reason is admission of calculators to exams in schools and universities. Casio and Texas Instruments basically have a cartel that dominates this market. Often one of these calculators is required.