- Understanding the key concept
- Does 12-54 to 13-56 gauge change require a re-setup?
- SUM function in a calculated column
- Difference Between 2 Dates (number of hours beyond 24 hours)
- mystery no crank, no start
- Car vibrates and has mild drone at 15-45 mph
- EFQ SQL error when using filedCondition on two different taxonomy terms
- Breathing trouble during high intensity
- Was a finger ever grown back with “pixie dust”?
- Did Hillary Clinton say that North Korea requires experienced diplomats rather than tweets?
- What is the industry standard way of calculating and annualizing performance metrics?
- Why the difference between SPY and ^GSPC?
- Feedback on Website Code
- Readable implementation of Trie in Python
- What were the other 8 Nazgul doing while the Witch-King weakened Arnor?
- Actors appearing in both Star Trek and Star Wars?
- How to query inside jsonb column
- Extract max of value in Fact table using date filter
- What are the .pgAdmin4.2123502176.addr and .log files?
- postgresql - Importing CSV Data with Custom Type
Solidity (Quick or Insertion) Sort
Is it crazy to feel the need to sort solidity arrays?
Imagine implementing a market (double action) you need to sort the orders. I could imagine other usecases where sort is useful. But as we all know even a for loop is dangerous in terms of gas exhaustion. What are best practices in this regard?
The search "Solidity Quicksort" returns nearly no results.
I came up with the idea of letting someone sort and upload the data back to the smart contract, then smart contract can just check if the data is right + sorted, which should be much easier than sorting. O(nlogn) versus O(n). The problem here is that the transaction size grows by O(n) now, which, I feel, could be problematic.
Any guidelines, experiences?